[BUG]: Mismatched type hints when using RDS Data API

[cmanou]

What version of drizzle-orm are you using?

0.30.1

What version of drizzle-kit are you using?

0.20.14

Describe the Bug

When using AwsDataApi pg driver which actually makes use of the type hints, there has been a bunch of queries that have resulted in mismatched hints. I have narrowed down the issue to the mergeQueries function in sql.ts

drizzle-orm/drizzle-orm/src/sql/sql.ts

Line 69 in 0ddab65

function mergeQueries(queries: QueryWithTypings[]): QueryWithTypings {

. This results in failed inserts and selects. In particular if the following if mergeQueries receives the following:

[
    { "sql": "(", "params": [] },
    { "sql": "default", "params": [] },
    { "sql": ", ", "params": [] },
    {
      "sql": ":1",
      "params": ["44562697-0b70-479c-8f38-f4ff9d17c537"],
      "typings": ["uuid"]
    },
    { "sql": ", ", "params": [] },
    {
      "sql": ":2",
      "params": ["value_2"]
    },
    { "sql": ", ", "params": [] },
    { "sql": ":3", "params": ["value_3"] },
    { "sql": ", ", "params": [] },
    {
      "sql": ":4",
      "params": ["{\"status\":\"enabled\"}"],
      "typings": ["json"]
    },
    { "sql": ", ", "params": [] },
    { "sql": "default", "params": [] },
    { "sql": ", ", "params": [] },
    { "sql": "default", "params": [] },
    { "sql": ", ", "params": [] },
    { "sql": "default", "params": [] },
    { "sql": ")", "params": [] }
  ]

This results in

{
    "sql": "(default, :1, :2, :3, :4, default, default, default)",
    "params": [
      "44562697-0b70-479c-8f38-f4ff9d17c537",
      "value_2",
      "value_3",
      "{\"status\":\"enabled\"}"
    ],
    "typings": ["uuid", "json"]
  }

Which has the typings indexes incorrect for when they are used later on by the dataapi session driver.

Expected behavior

Expected the result from merge queries to be similar to this, or potentially but would require more work is making it such that the typings stick with the params?

{
    "sql": "(default, :1, :2, :3, :4, default, default, default)",
    "params": [
      "44562697-0b70-479c-8f38-f4ff9d17c537",
      "value_2",
      "value_3",
      "{\"status\":\"enabled\"}"
    ],
    "typings": ["uuid",undefined, undefined, "json"]
  }

Environment & setup

No response

[zacronos]

I seem to have just hit this bug, which results in my "typeHint":"TIMESTAMP" hints showing up on the wrong parameters, and leaving my actual TIMSTAMP/Date parameters being treated as strings. This causes me to get this error: ERROR: column "updated_at" is of type timestamp without time zone but expression is of type character varying on what should be a valid query.

I'm using v0.30.7.

[cmanou]

@AndriiSherman @AlexBlokh I would be willing to help move this forward just wondering if you have had thoughts on the approach and why typings weren't initially passed around with the actual params?

[cmanou]

@dankochetov I see you were working on some data api fixes in #2119 do you have thoughts on the best approach here ?

[dankochetov]

@cmanou could you provide an example query that triggers this behavior?

[zacronos]

I know this is a description rather than an example, but I believe it occurs any time you have a query that will generate a list of parameters where some parameters do not have type hints, followed by parameters which do have type hints. The type hints then get associated with the earlier parameters instead of the correct ones.

[cmanou]

Lots off different ones this particular one was:

export const calendar = pgTable('calendars', {
  id: uuid('id')
    .primaryKey()
    .default(sql`gen_random_uuid()`),

  orgMembershipId: prefixedUlid('om_id', { prefix: 'om' })
    .notNull()

  platform: text('platform').notNull(),
  externalId: text('external_id').notNull(),
  externalData: json('external_data').notNull(),

  updatedAt: timestamp('updated_at')
    .notNull()
    .default(sql`now()`),
  createdAt: timestamp('created_at')
    .notNull()
    .default(sql`now()`),
});

export const prefixedUlid = <Prefix extends string, PrefixedUlid = `${Prefix}_${string}`>(
  name: string,
  opts: { prefix: Prefix },
) =>
  customType<{ data: PrefixedUlid; driverData: string }>({
    dataType: () => 'uuid',
    toDriver: (value) => {
      const regex = new RegExp(`^${opts.prefix}_([0-7][0-9a-hjkmnp-tv-zA-HJKMNP-TV-Z]{25})$`);
      const match = (value as string).match(regex);
      if (!match || match[1] === undefined) {
        throw new Error(`Invalid format`);
      }

      return ULIDtoUUID(match[1]);
    },
    fromDriver: (value) => {
      return `${opts.prefix}_${UUIDtoULID(value)}` as PrefixedUlid;
    },
  })(name);

  const [result] = await db
    .insert(calendars)
    .values({
      orgMembershipId,
      platform,
      externalId,
      externalData,
    })
    .returning();
    ```

But as @zacronos said this happens whenever you use queries that have a mix of type hints and non type hint variables. I believe other people have reported similar issues with selects and limits having wrong type hints with the data api and am generally convinced that the mergeQueries and how typeHints are linked to there actual values is the problem

[zacronos]

I'm pretty confident in the mergeQueries theory as well. When I hit a problem with this, based on @cmanou 's description of the underlying cause, I was able to fix my query by reordering things such that the parameters which required typeHints were all before the ones that did not.

[cmanou]

@dankochetov Have you had anymore thoughts on this? Happy to help if you have a particular direction.

[cmanou]

@dankochetov Just wondering if you have had anymore thoughts on this it basically makes data api un-usuable which is a shame. As I said I'm willing to work on the sulotion just wondering if you had a preference on the approach ie allow undefined or pass the hints with their values all the way through?

[cmanou]

Okay based off the brief discussion in discord theoretically this shouldn't be happening because the typings should be filled with 'none' type but it turns out for placeholders and cases where drizzle builds internal params such as for relationships

drizzle-orm/drizzle-orm/src/pg-core/dialect.ts

Line 349 in 0ddab65

const limitSql = limit ? sql` limit ${limit}` : undefined;

the type isn't add in these too lines

drizzle-orm/drizzle-orm/src/sql/sql.ts

Line 220 in 0ddab65

return { sql: escapeParam(paramStartIndex.value++, chunk), params: [chunk] };

drizzle-orm/drizzle-orm/src/sql/sql.ts

Line 251 in 0ddab65

return { sql: escapeParam(paramStartIndex.value++, chunk), params: [chunk] };

Updating them to have ['none'] as the types resolves the issue but feels incorrect as really we should be trying to use prepareTyping but for a placeholder the type is not really known, so although this fix would work for my use cases it does not work if people are using types such as uuid with preparedQueries

[dankochetov]

@zacronos could you test if it works with drizzle-orm@beta?

[zacronos]

If I had a convenient query, I would love to help -- unfortunately I've entirely forgotten which query was the source of the problem for me, and we're swamped with customer onboarding at the moment.

[AndriiSherman]

should be fixed in drizzle-orm@0.31.3. If you still see this issue, please reopen it