feat: optionally support unquoted identifiers #45
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.
Description
The default state is to quote all identifiers in SQL statements. This is a reasonable default. There are circumstances where it's beneficial to let the database handle the casing their own way to maintain compatibility across DBMSes. This feature allows a non-default configuration option to be set on the dialector which does not quote identifiers and lets Oracle auto uppercase them.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Tested with a product which is database agnostic and relies on default database casing rules. Verified that all existing tests continue to pass (proving that the default behavior remains unchanged).