fix: Support new Postgres index API #13
Merged
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.
Drizzle 0.31.0 introduced a breaking change to the Postgres indexes API. The lack of support in
drizzle-dbml-generator
for enriched "extra config" columns led to two failure scenarios with the current build:tbl.f1.asc()
(asc()
not found in standard column type)drizzle-orm
calls to use the indexes. JSON parsing would fail since thedefaultConfig
on a given column wasn't being set or enriched.What has changed
drizzle-orm
dev-dependency to the latest version (0.31.1
)ExtraConfigColumns
symbol. This is specific to Postgres but functionally works in a dialect-agnostic way.extraConfig
→extraConfigBuilder
to make language clearer and more accurateresolves #12