Add Drizzle beta v1 support

[ziahamza]

Summary

The PR adds support for Drizzle v1 beta relational queries through relations + db.query, while keeping the existing 0.44.x behavior intact and exposing db._query as an alias on the 0.44.x path.

[changeset-bot]

🦋 Changeset detected

Latest commit: 53924bf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@powersync/drizzle-driver	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Chriztiaan]

Hey @ziahamza, firstly thank you for putting in the effort and making this PR. In terms of an official release, we would prefer to wait for the stable Drizzle 1.0.0 version and then only support that instead of keeping support for 0.x.x versions, to make adoption and maintenance easier on our side.

As an alternative, we could do dev releases off this PR and update it as changes from the upstream Drizzle project trickles down on the way to the v1 release. That would mean the work needed for this current PR includes a changeset entry, and potentially dropping all the backwards compatible code/documentation/tests you have added here. I suspect that might also simplify your implementation if you only had to worry about support v1 instead of backwards compatibility?

[ziahamza]

Hey @ziahamza, firstly thank you for putting in the effort and making this PR. In terms of an official release, we would prefer to wait for the stable Drizzle 1.0.0 version and then only support that instead of keeping support for 0.x.x versions, to make adoption and maintenance easier on our side.

As an alternative, we could do dev releases off this PR and update it as changes from the upstream Drizzle project trickles down on the way to the v1 release. That would mean the work needed for this current PR includes a changeset entry, and potentially dropping all the backwards compatible code/documentation/tests you have added here. I suspect that might also simplify your implementation if you only had to worry about support v1 instead of backwards compatibility?

Yes it will indeed simplify things a lot if we go all into v1 and drop backward compat support! Let me prepare the dev release with the correct change set to get the dev release out for projects already migrating to drizzle v1 beta