You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PostgreSQL native parameter placeholders are $1, $2, etc. This is different from the e.g. ODBC placeholders (?, ?), which are also positional but not numbered (i.e. PG allows referring to the same parameter more than once, whereas ODBC does not). Unfortunately, our current placeholder logic currently doesn't allow for (command) state to participate in the generation (i.e. what's the next number).
Assuming we want to do this, it would probably be done along with #22458, which is about some cleanup of the placeholder logic.
Note: Npgsql also supports named placeholder (@foo), by rewriting them to the native PG placeholders. This issue would allow us to stop doing that.
The text was updated successfully, but these errors were encountered:
PostgreSQL native parameter placeholders are $1, $2, etc. This is different from the e.g. ODBC placeholders (?, ?), which are also positional but not numbered (i.e. PG allows referring to the same parameter more than once, whereas ODBC does not). Unfortunately, our current placeholder logic currently doesn't allow for (command) state to participate in the generation (i.e. what's the next number).
Assuming we want to do this, it would probably be done along with #22458, which is about some cleanup of the placeholder logic.
Note: Npgsql also supports named placeholder (@foo), by rewriting them to the native PG placeholders. This issue would allow us to stop doing that.
The text was updated successfully, but these errors were encountered: