Skip to content

Conversation

@levkk
Copy link
Collaborator

@levkk levkk commented Nov 30, 2025

  • feat: add support for inserting pgdog.unique_id() pretty much anywhere in the query
  • feat: unique_id generation is now sync, so it can be used anywhere
  • chore: move PREPARE/EXECUTE support into new rewrite engine
  • chore: started moving INSERT splitting into new engine (not ready)
  • chore: clippy

@blacksmith-sh

This comment has been minimized.

@levkk levkk changed the title Query rewrite engine 3.0 Query rewrite engine 3.0 (part 1 of many) Dec 1, 2025
@blacksmith-sh

This comment has been minimized.

@levkk levkk force-pushed the levkk-rewrite-3.0 branch from 601478e to 8566374 Compare December 2, 2025 21:02
@levkk levkk force-pushed the levkk-rewrite-3.0 branch from a2c9ec8 to 1949aa8 Compare December 3, 2025 19:52
@blacksmith-sh

This comment has been minimized.

levkk added a commit that referenced this pull request Dec 8, 2025
Refactor the query parser to be completely recursive. Use the same
parser for `SELECT` and `DELETE` queries. This adds support for
extracting the sharding key filter from pretty much anywhere in the
query, as long as it follows our supported format:

```sql
key = $1 OR key IN ($1, $2, $3) OR key = ANY($1)
```

fix #653 

TODOs:

1. Use new parser for `UPDATE` and `INSERT` statements. Requires
integration with #637 (split rewrite engine from parser).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants