Consolidate and rationalize SQL generation #2493
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-unknown
Milestone
Currently different parts of the stack do SQL generation in different ways. This may be fine since, for example, query and update have different mechanisms and requirements. However, we should make sure that we are using common code where it makes sense. If nothing else, code for escaping, etc. should be able to be shared. Related to this is that if a provider needs to customize how things like escaping are done, then the provider should only need to do this in one place.
The text was updated successfully, but these errors were encountered: