Does introspect only generate schema in the "out" (./drizzle) directory?

My config looks like this:

export default defineConfig({
    dialect: 'postgresql',
    schema: './src/lib/server/db/schema.ts',
    dbCredentials: {
        url: process.env.POSTGRES_URL
    },
    verbose: true,
    strict: true,
})

export default defineConfig({
    dialect: 'postgresql',
    schema: './src/lib/server/db/schema.ts',
    dbCredentials: {
        url: process.env.POSTGRES_URL
    },
    verbose: true,
    strict: true,
})

But if I run introspect, it always generates in ./drizzle
Am I doing something wrong or is this expected?

francis•8/10/24, 2:43 AM

it's always been that way for me, I have a package script to generate the schema and copy it to the target

Darren•8/10/24, 11:56 AM

change to:

Darren•8/10/24, 11:57 AM

Chris SoulOP•8/10/24, 12:02 PM

Wouldn't that also put all the migrations there? I only want the schema

Darren•8/10/24, 12:04 PM

well you can just change it to './src/lib/server/db' it will overwrite your exisitng schema and relatiopn file tho, which is prob not what you want

Darren•8/10/24, 12:10 PM

but if you want to keep all your migrations seperate and only diff for introspect then you can either use a seperate config file and specify on cli using introspect --config=intro.config.ts or using introspect --out=src/lib/server/db/

Chris SoulOP•8/10/24, 5:19 PM

I think I'm overengineering it at this point

I don't need to introspect that often so I'll just manually move them

Chris SoulOP•8/10/24, 5:20 PM

Thank you both though!

francis•8/10/24, 7:19 PM

here's my commands, fyi

francis•8/10/24, 7:19 PM

(in a package.json script)

francis•8/10/24, 7:20 PM

is an intermediate step I put in that runs

sed

sed

over the output to change some things - e.g. introspect always pulls timestamp columns in 'string' mode, so I have to fix those

francis•8/10/24, 7:20 PM

I recommend setting that sort of thing up since it's relatively easy to do and have it be consistent