Fix bug #246

[TanguyFir]

Like the title said, it fixes the issue #246. SafeQL should distinguish schema in table/column resolution.

To discuss :

• how to deal with the default schema ? for now I hard coded public but cannot work for all use cases

Available solutions :

• put a default schema option for the plugin with a default value to public
• use the current behaviour (do not take into account schema) when schemaname is not defined

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: fddfc5c24ba49582b1e46611b4fc9d4b5a8196bf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

| Name | Status | Preview | Comments | Updated (UTC) | | :--- | :----- | :------ | :------- | :------ | | **safeql** | ⬜️ Ignored ([Inspect](https://vercel.com/newbie012s-projects/safeql/YbqUSrj81tnYNvbbVLozevAQB4Cu)) | [Visit Preview](https://safeql-git-fork-tanguyfir-fix-bug-246-newbie012s-projects.vercel.app) | | Jul 25, 2024 4:04pm |

[TanguyFir]

@Newbie012 When do you think you can merge this PR and release a new version ?