[SQLite] Fix onConflict targets

[wkunert]

As reported in #410 upserts are failing when using SQLite. @krzysztofciombor already identified the root cause (missing parentheses around the target), this PR delivers the proposed fix and corresponding tests.

[AndriiSherman]

@wkunert thanks a lot!
Also thanks for getting tests for each driver. Looks good to be merged

Right after @dankochetov will check - will include in in main and next release we will have

[hirvesh]

Hey guys, I think there's an issue here with composite primary keys where now we end up with double parentheses. See example schema and query generated below and associated error:

export const posts = sqliteTable("posts", {
  id: text("id").notNull(),
  siteId: text("siteId").notNull().references(() => sites.id, { onDelete: "cascade" }),
  title: text("title"),
  content: text("content"),
  slug: text("slug").notNull(),
  createdAt: integer("createdAt", { mode: "timestamp_ms" }),
  updatedAt: integer("updatedAt", { mode: "timestamp_ms" }),
  readyToPublish: integer("readyToPublish").default(0),
  publishDate: integer("publishDate", { mode: "timestamp_ms" }),
}, (posts) => ({
  compositePk: primaryKey(posts.id, posts.siteId)
}));

db.insert(posts)
.values({
  id: postIds[index],
  siteId: siteWithAccount.sites.id,
  title: getPageTitle(post.value),
  content: JSON.stringify(post.value),
  slug: getSlug(siteWithAccount.sites.id, getPageTitle(post.value)),
})
.onConflictDoUpdate({
  target: [posts.id, posts.siteId],
  set: {
    title: getPageTitle(post.value),
    content: JSON.stringify(post.value),
    slug: getSlug(siteWithAccount.sites.id, getPageTitle(post.value)),
  }
})
.run()

insert into "posts" ("id", "siteId", "title", "content", "slug") values (?, ?, ?, ?, ?) on conflict (("posts"."id", "posts"."siteId")) do update set "title" = ?, "content" = ?, "slug" = ?

See double parentheses added above, which causes error: ON CONFLICT clause does not match any PRIMARY KEY or UNIQUE constraint.

Opened bug report: #518

[wkunert]

Thank you @hirvesh for the analysis – I created a PR with a fix (#521).