[BUG]: INSERT INTO … SELECT does not work with generated columns

[hyunbinseo]

Report hasn't been filed before.

• I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?

0.38.4

What version of drizzle-kit are you using?

0.30.2

Other packages

No response

Describe the Bug

Reproduction. Use the mre-0 branch.

# Node.js 23
node src/index.ts

# Node.js 22
node --experimental-strip-types src/index.ts

import { db } from './db/index.ts';
import { userTable } from './db/schema.ts';

await db // works
  .insert(userTable)
  .values({ deactivatedAt: new Date() })
  .returning();

await db // fails
  .insert(userTable)
  .select(db.select({ deactivatedAt: userTable.deactivatedAt }).from(userTable));

Error: Insert select error: selected fields are not the same or are in a different order compared to the table definition (at SQLiteInsertBuilder.select)

• Feat: Support insert into ... select syntax #2783

// schema.ts
import { sql, type SQL } from 'drizzle-orm';
import { integer, sqliteTable } from 'drizzle-orm/sqlite-core';

export const userTable = sqliteTable('user', {
  id: integer().primaryKey(),
  deactivatedAt: integer({ mode: 'timestamp' }),
  isDeactivated: integer({ mode: 'boolean' }) //
    .generatedAlwaysAs((): SQL => sql`${userTable.deactivatedAt} IS NOT NULL`),
});

[dakdevs]

This is killing me rn with MySQL :(

[WilcoKruijer]

Seems like INSERT INTO ... SELECT always needs to match precisely all columns of the table, which does not make sense considering generated columns but also nullable columns and columns with defaults.