RQB v2 #3974
Open
RQB v2 #3974
+75,238
−5,005
Conversation
This file contains 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
…to rqb-v2-orm36
…` field, RQB v1 entities to `_relations.ts`, added template to SQLWrapper for return type inferrence, switched RQB-related local tests & type tests to use `._query`
…thReplicas()` compatibility (to be reworked), switched tests to use `_query` method for RQB v1 tests
… fixed, simplified query builders, added JSON parsing for top level SQLite response mapper, fixed aggregated relation count sql
… relational configs, resolved potential type overlaps with similar table names from different schemas on query results, resolved relation builders allowing usage of columns from table with same name from different schema
…nt relations' `where.$raw` callback
…ypes to tables instead of column records, relational tests v2 for postgresql, updated relations .where field names, added error on nothing selected from table in relational queries v2
…to rqb-v2-orm36
…http `$withAuth` rqbv2 tests
…ntity kinds, new `orderBy` api
…RQB V2, removed unnecessary argument from `WithContainer` generics
…ional relation results, added forced relation optionality for queries with additional filters, fixed libsql rqb pre-mapping and transaction result mapping, added libsql RQBv2 tests, added new RQB test cases related to aforementioned changes
…joins and `json_arrayagg()`'s `order by` order preservation, removed unused code, added error throw to incomplete RQBv2 feature `.through()`
…regated relations
…d planetscale tests for RQB v2, added common RQB tests for pg dialect drivers
…non-optional relations, defaulted relations to optional, allowed full booleans in RQB query config's `with` section, moved `coalesce` in pg RQB for consistency
…proxy session RQB fixes, fixed missing `TRelations` arguments in generics
…plified RQB column builder for `MySQL`
…, RQBv2 schema tests
…lback getting columns passed to first argument instead of full table
…to rqb-v2-orm36
|
Great work! |
this problem does not exist is rqb v2 |
|
This is so exciting. What a coincidence I'm here only 3 minutes after the latest check!! |
…itched `sql-js` prepare logic to query-builder-side preparation instead of db-side because of the need to free connections manually
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.
Features:
sqlprefixing aliased tables with schema namesgetTableUniqueName(table)SQLWrapperneon-http-batchtestssql-jsprepare logic to query-builder-side preparation instead of db-side because of the need to.free()connections manuallyBreaking changes:
singlestore's, gained 2 additional generic arguments for RQB v2 queriesDrizzleConfiggeneric withTRelationsargument andrelations: TRelationsfielddb.query=>db._querydrizzle-orm,drizzle-orm/relationstodrizzle-orm/_relationswith RQB v2's alternatives (if such exist) being put in their place:${dialect}-core/query-builders/queryfiles were moved to${dialect}-core/query-builders/_querywith RQB v2's alternatives being put in their place.free()fromsql-js