6 replies

`no such table: user` in production with drizzle + sqlite + next.js?

i have 2 sqlite databases:

1.

example.dev.sqlite

example.dev.sqlite

- for development
2.

example.prod.sqlite

example.prod.sqlite

- for production

i know how to use drizzle in development but i'm having a problem in production.

in development, i do

pnpm db:generate

pnpm db:generate

to generate migrations &

pnpm db:push

pnpm db:push

to create tables.

what should i do in production to generate tables? do i have to run the same

pnpm db:push

pnpm db:push

script?

my sqlite file is in docker swarm so the location is a bit different.

my

drizzle.config.ts

drizzle.config.ts

file looks like:

import * as dotenv from "dotenv"
import type { Config } from "drizzle-kit"
// bug in drizzle: see https://github.com/drizzle-team/drizzle-orm/issues/1228
// import { DATABASE_PATH } from '@/app/lib/env/server'

dotenv.config({ path: ".env.development" })

const DATABASE_PATH = process.env.DATABASE_PATH

export default {
    schema: "./src/app/db/schema.ts",
    out: "./src/app/db/migrations",
    driver: "better-sqlite",
    dbCredentials: {
        url: DATABASE_PATH,
    },
    verbose: true,
} satisfies Config

import * as dotenv from "dotenv"
import type { Config } from "drizzle-kit"
// bug in drizzle: see https://github.com/drizzle-team/drizzle-orm/issues/1228
// import { DATABASE_PATH } from '@/app/lib/env/server'

dotenv.config({ path: ".env.development" })

const DATABASE_PATH = process.env.DATABASE_PATH

export default {
    schema: "./src/app/db/schema.ts",
    out: "./src/app/db/migrations",
    driver: "better-sqlite",
    dbCredentials: {
        url: DATABASE_PATH,
    },
    verbose: true,
} satisfies Config

would i need to change

DATABASE_PATH

DATABASE_PATH

. im confused here as i am unable to get it to work in production?

my goal is to simply get the production sqlite database working. if anyone has done it before, lmk what's the process? google didn't help much.

`no such table: user` in production with drizzle + sqlite + next.js?

i have 2 sqlite databases:

1.

example.dev.sqlite

example.dev.sqlite

- for development
2.

example.prod.sqlite

example.prod.sqlite

- for production

i know how to use drizzle in development but i'm having a problem in production.

in development, i do

pnpm db:generate

pnpm db:generate

to generate migrations &

pnpm db:push

pnpm db:push

to create tables.

what should i do in production to generate tables? do i have to run the same

pnpm db:push

pnpm db:push

script?

my sqlite file is in docker swarm so the location is a bit different.

my

drizzle.config.ts

drizzle.config.ts

file looks like:

import * as dotenv from "dotenv"
import type { Config } from "drizzle-kit"
// bug in drizzle: see https://github.com/drizzle-team/drizzle-orm/issues/1228
// import { DATABASE_PATH } from '@/app/lib/env/server'

dotenv.config({ path: ".env.development" })

const DATABASE_PATH = process.env.DATABASE_PATH

export default {
    schema: "./src/app/db/schema.ts",
    out: "./src/app/db/migrations",
    driver: "better-sqlite",
    dbCredentials: {
        url: DATABASE_PATH,
    },
    verbose: true,
} satisfies Config

import * as dotenv from "dotenv"
import type { Config } from "drizzle-kit"
// bug in drizzle: see https://github.com/drizzle-team/drizzle-orm/issues/1228
// import { DATABASE_PATH } from '@/app/lib/env/server'

dotenv.config({ path: ".env.development" })

const DATABASE_PATH = process.env.DATABASE_PATH

export default {
    schema: "./src/app/db/schema.ts",
    out: "./src/app/db/migrations",
    driver: "better-sqlite",
    dbCredentials: {
        url: DATABASE_PATH,
    },
    verbose: true,
} satisfies Config

would i need to change

DATABASE_PATH

DATABASE_PATH

`no such table: user` in production with drizzle + sqlite + next.js?

Similar Threads

`no such table: user` in production with drizzle + sqlite + next.js?

Similar Threads

Similar Threads

Similar Threads