Numeric Operators in SQL Where clauses
> On Feb 2, 2018, at 1:35 PM, Alex Clay <email@example.com> wrote:
> Please define “generic sql.” 😉
> There are multiple SQL specifications with different levels of conformance and every backend implements these specifications quite differently. Are you trying to build your app to support multiple SQL engines? If so, I hope it’s for a very good business reason because doing so is a pain.
So the idea of “Sticking to Generic SQL” is not really a possibility?
My business reason is to have less work in case of a client wanting to use something OTHER THAN Postgres. To me Postgres is the bomb because it’s Free and Powerful, it stands up to the big time yet it’s internationally sourced and I get a good feeling from it overall. But I thought I could stay as generic as possible to avoid having to do MORE coding should I encounter a port situation. That’s all. Trying to think ahead.
What you say, I have heard before. Kelly told me that different backends implement the standards differently..act differently given the same command. He too said what you are saying.
Yet another person with a lot of knowledge told me to stick to the standard as much as possible and it sounded like good advice.
So…. Where am I left standing ? I don’t know. If I just lazily stick only to Postgres don’t I paint my app into a Postgres only corner, or face a hell of a lot of work to move it to another?