• Add comprehensive tests for schema-qualified joins in query builder
• Test schema inclusion in regular inner joins with multiple entities
• Test schema inclusion in subquery joins with nested relationships
• Verify correct SQL generation with proper schema prefixes

Main test suite for schema-qualified joins

• Created test suite for multi-schema joins with two test cases
• First test validates schema inclusion in regular inner joins between Lesson, _StudyPlanCourse, and
 Course entities
• Second test validates schema inclusion in subquery joins with nested relationships
• Both tests verify SQL generation contains proper schema-qualified table names and execute
 successfully

test/functional/multi-schema-and-database/custom-schema-joins/custom-schema-joins.test.ts

Course entity with custom schema

• Define Course entity with schema "myschema"
• Include id as primary column and name as regular column

test/functional/multi-schema-and-database/custom-schema-joins/entity/Course.ts

Lesson entity with custom schema

• Define Lesson entity with schema "myschema"
• Include auto-generated id, courseId foreign key, and duration columns

test/functional/multi-schema-and-database/custom-schema-joins/entity/Lesson.ts

Description

The test inserts Lesson rows with an explicit id even though id is
@PrimaryGeneratedColumn(). On MSSQL this causes TypeORM to wrap the INSERT in `SET IDENTITY_INSERT
... ON/OFF`, which is unrelated to the join-schema behavior being tested and can introduce avoidable
brittleness.

Code

test/functional/multi-schema-and-database/custom-schema-joins/custom-schema-joins.test.ts[R36-38]

+                await connection
+                    .getRepository(Lesson)
+                    .save({ id: 1, courseId: "c1", duration: 60 })

Evidence

The test explicitly sets id: 1 for Lesson even though the entity uses an auto-generated primary
key. TypeORM has explicit logic to enable IDENTITY_INSERT on MSSQL when an explicit value is
provided for an auto-increment PK, meaning this test will execute extra MSSQL-specific statements as
part of its setup.

test/functional/multi-schema-and-database/custom-schema-joins/custom-schema-joins.test.ts[36-38]
test/functional/multi-schema-and-database/custom-schema-joins/custom-schema-joins.test.ts[72-75]
test/functional/multi-schema-and-database/custom-schema-joins/entity/Lesson.ts[3-6]
src/query-builder/InsertQueryBuilder.ts[755-773]
src/query-builder/InsertQueryBuilder.ts[1008-1025]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The tests insert `Lesson` entities with an explicit `id` even though `Lesson.id` is a `@PrimaryGeneratedColumn()`. On MSSQL, this triggers TypeORM to wrap inserts with `SET IDENTITY_INSERT ... ON/OFF`, adding extra MSSQL-specific statements and potential brittleness unrelated to the join-schema assertions.

### Issue Context
The tests only need `courseId` and `duration` to validate join generation and query results; `id` is not used.

### Fix Focus Areas
- test/functional/multi-schema-and-database/custom-schema-joins/custom-schema-joins.test.ts[36-38]
- test/functional/multi-schema-and-database/custom-schema-joins/custom-schema-joins.test.ts[72-75]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools