Conversation
…, `node-pg` codecs; root level of RQBv2 queries in PG is no longer treated as in-JSON, unless explicitly stated otherwise [other dialects pending], extended test postpone date, generic codecs improvements
…to regular select queries, deleted some deprecated column mappers or overloads [WIP], codec tests for `bun-sql/pg`
…led `bytea` codec test in `neon-http`
…pg` driver's version
…not supported by environment, explicit `noop` flag for mappers
…oper `noop` mapper handling, fixed `pglite` codecs, code cleanup
…ion & old api deprecation notices to custom pg column
…r PG custom columns, extended postpone dates
…orm/pg-core/utils` to `drizzle-orm/pg-core/array`), reworked launchers of import tests
…or single table queries
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
postgres- resolves issues created by differences of data types returned by different drivers or different contexts of query (regular select, JSON object, postgres array). Currently only handles supported by drizzle constructors column types.postgresdb._query) frompostgresmakePgArray,parsePgArray) fromdrizzle-orm/pg-core/utils[/array]todrizzle-orm/pg-core/arraypostgressessions & prepared queriesneon-httpbyteadata corruptionbun-sql/postgrestimestamp timezone truncation,json[b]data double stringification