volcanicislander
volcanicislander
PostsComments
DTDrizzle Team
Created by SKUZZIE on 11/6/2024 in #help
Do prepared statement names matter?
      return db
        .select()
        .from(schema.relief)
        .where(...)
        .orderBy(schema.relief.startsAt) .prepare('get_relief_by_times_and_position')
        .execute({ startsAt, endsAt, positionId, reliefIn });
      return db
        .select()
        .from(schema.relief)
        .where(...)
        .orderBy(schema.relief.startsAt) .prepare('get_relief_by_times_and_position')
        .execute({ startsAt, endsAt, positionId, reliefIn });
40 |     res = resolve
41 |     rej = reject
42 |   }).catch((err) => {
43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
44 |     // application that created the query
45 |     Error.captureStackTrace(err)
               ^

error: Prepared statements must be unique - 'get_relief_by_times_and_position' was used for a different statement

      at <anonymous> (/app/node_modules/pg-pool/index.js:45:11)
40 |     res = resolve
41 |     rej = reject
42 |   }).catch((err) => {
43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
44 |     // application that created the query
45 |     Error.captureStackTrace(err)
               ^

error: Prepared statements must be unique - 'get_relief_by_times_and_position' was used for a different statement

      at <anonymous> (/app/node_modules/pg-pool/index.js:45:11)
@Angelelz Apologies for resurrecting this thread but I've recently converted a bunch of queries into prepared statements and am getting errors like this. Should I ensure the prepared statement name is unique, possibly by parameterizing it like it was a cache key?
8 replies