Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

src/decorator/options/ColumnOptions.ts (1)

191-196: Clarify JSDoc, fix grammar/casing, and scope the option to virtual columns

• “entities alias” → “entity alias”
• Use the standard “@see”
• This is evaluated at SELECT time (not “generating the relational db script”)
• Note it only applies to mode "virtual" or "virtual-property" and add a short security note

Apply this diff to tighten up the docs:

-    /**
-     * Query to be used to populate the column data. This query is used when generating the relational db script.
-     * The query function is called with the current entities alias either defined by the Entity Decorator or automatically
-     * @See https://typeorm.io/decorator-reference#virtualcolumn for more details.
-     */
+    /**
+     * SQL fragment used to populate the value of a virtual column when reading data (SELECT).
+     * Only applies to columns with mode "virtual" or "virtual-property".
+     * The function receives the current entity alias (from QueryBuilder) to reference other columns.
+     * @see https://typeorm.io/decorator-reference#virtualcolumn
+     *
+     * Security note: never concatenate untrusted input here; this string is interpolated into the SQL.
+     */
     query?: (alias: string) => string

test/functional/entity-schema/columns/virtual-columns/virtual-columns.ts (1)

24-34: Make the test resilient to driver differences by not hard-coding id=0

Some drivers or configurations may not accept an explicit 0 for an auto-increment primary key. Capture the generated id from save() and read back by that id to avoid flakiness and improve portability.

-                await repo.save({ id: 0, k1: 1 })
-                const result = (await repo.findOne({ where: { id: 0 } }))!
+                const created = await repo.save({ k1: 1 })
+                const result = await repo.findOneByOrFail({ id: created.id })
                 expect(result.vK1).eq(result.k1)
                 expect(result.vK1).eq(1)

test/functional/entity-schema/columns/virtual-columns/entity/Activity.ts (1)

18-20: Avoid hard-coded identifier quoting to improve cross-driver portability

Double-quoted identifiers work for SQLite/Postgres but not MySQL. Since the test runs on better-sqlite3 today but the feature is cross-driver, prefer an unquoted expression to reduce driver-specific syntax. The alias is provided by TypeORM and should be used as-is.

-            query: (alias) =>
-                `SELECT k1 FROM "activities" WHERE "k1" = ${alias}."k1"`,
+            query: (alias) =>
+                `SELECT k1 FROM activities WHERE k1 = ${alias}.k1`,

src/entity-schema/EntitySchemaTransformer.ts (1)

101-101: Clarify precedence or enforce exclusivity when multiple special modes are set

virtualProperty is evaluated last, overriding other modes like createDate, updateDate, etc. If a column mistakenly sets multiple flags, the last one “wins”, which can hide configuration errors. Consider throwing or logging when virtualProperty is combined with other special modes, or document the intended precedence.

If you want, I can add a guard to error on conflicting modes (virtualProperty + any of createDate/updateDate/deleteDate/version/treeChildrenCount/treeLevel/objectId) and a small test asserting the error.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled
• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.