Migrations against Local Turso

I am currently running a local Turso instance with

turso dev

turso dev

. How do I go about seeding it with

drizzle-kit

drizzle-kit

?

Here's my config so far:

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  schema: "./src/drizzle",
  out: "./migrations",
  dialect: "turso",
  dbCredentials: {
    url: "http://localhost:8080/",
  },
});

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  schema: "./src/drizzle",
  out: "./migrations",
  dialect: "turso",
  dbCredentials: {
    url: "http://localhost:8080/",
  },
});

When I run

drizzle-kit push

drizzle-kit push

, I get

LibsqlError: SQL_INPUT_ERROR: SQL input error: no such column: value (at offset 121)

LibsqlError: SQL_INPUT_ERROR: SQL input error: no such column: value (at offset 121)

, whether or not the

migrations

migrations

directory exists. My credentials do seem to be fine, as the ORM appears to connect fine at runtime.

Just tested, this also happens when running against a remote Turso DB too

Drizzle Team•14mo ago

Hello, I’m Allie!

Migrations against Local Turso

I am currently running a local Turso instance with

turso dev

turso dev

. How do I go about seeding it with

drizzle-kit

drizzle-kit

?

Here's my config so far:

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  schema: "./src/drizzle",
  out: "./migrations",
  dialect: "turso",
  dbCredentials: {
    url: "http://localhost:8080/",
  },
});

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  schema: "./src/drizzle",
  out: "./migrations",
  dialect: "turso",
  dbCredentials: {
    url: "http://localhost:8080/",
  },
});

When I run

drizzle-kit push

drizzle-kit push

, I get

LibsqlError: SQL_INPUT_ERROR: SQL input error: no such column: value (at offset 121)

LibsqlError: SQL_INPUT_ERROR: SQL input error: no such column: value (at offset 121)

, whether or not the

migrations

migrations

directory exists. My credentials do seem to be fine, as the ORM appears to connect fine at runtime.

Just tested, this also happens when running against a remote Turso DB too

Migrations against Local Turso

Similar Threads

Migrations against Local Turso

Similar Threads

Similar Threads

Similar Threads