uql-migrate against libsql+sqld will fail

[suau]

This is separate issue from #86,
When migrating against libsql running sqld (over http instead of local file)
The generate (and here manually fixed escapes for testing):

import type { SqlQuerier } from "uql-orm/migrate";

/**
 * Migration: schema
 * Created: 2026-04-04T11:44:01.078Z
 * Generated from entity definitions
 */
export default {
  async up(querier: SqlQuerier): Promise<void> {
    await querier.run(`CREATE TABLE \`Article\` (
  \`id\` INTEGER PRIMARY KEY AUTOINCREMENT,
  \`title\` TEXT,
  \`content\` TEXT
);
CREATE INDEX \`idx_Article_title\` ON \`Article\` (\`title\`);`);
  },

  async down(querier: SqlQuerier): Promise<void> {
    await querier.run(`DROP TABLE IF EXISTS \`Article\`;`);
  },
};

This will fail, because sqld does not support multiple statements.
breaking it up with multiple await querier.run() does fix the issue

[suau]

I will add another issue here, since it is what lead me to the main issue here and is related to the sqld limitations.
assuming this uql.config.ts file:

import type { Config } from "uql-orm";
import { LibsqlQuerierPool } from "uql-orm/libsql";
import { Article } from "./src/api/db/entities/article";

export default {
  pool: new LibsqlQuerierPool({
    url: "file:tmp/local.db",
    syncUrl: process.env.LIBSQL_URL,
    syncInterval: 60,
  }),
  entities: [Article],
  migrationsPath: "./migrations",
} satisfies Config;

This setup will read from file:tmp/local.db and write to process.env.LIBSQL_URL, writes will eventually sync to tmp/local.db.
This migration will also fail, I'm not sure if that's what's happening, but removing the sync temporarily and setting the url to process.env.LIBSQL_URL will make sure to directly apply the migration to sqld. I think the migrator should recognize this pattern and execute the migration on the syncUrl.

[rogerpadilla]

Thank you for the report.

Fixed in v0.8.2.
sqld (HTTP) effectively expects one SQL statement per execute/run. UQL v0.8.2+ now emit one await querier.run("…") per statement in entity-generated migrations.

For LibSQL embedded replicas (file: + syncUrl), LibsqlQuerierPool.getMigrationQuerier now targets syncUrl for migrations and uql_migrations, while getQuerier stays on the local replica. Call sites use acquireQuerierForMigrations so Migrator and DatabaseMigrationStorage stay consistent. Introspection / getDiffs still use the normal pool connection (typically local).

Let me know if that releases properly addressed the issues or reopen this.

Closed by #88