SQLite Update to get it closer to Postgres with ecto.

[jeregrine]

I'm bringing the discussion here, changes so far and work todo

• DISTINCT is supported, just not column wise, need to check that distinct is called like MYSQL with distinct: true only
  • remove order by code I added
• Converted JSON types to TEXT
• Added Proper casing to REALS
• Adding parens around sub commands for consistency with Postgres. (NOT union/except/intersect)
• STARTED adding actual errors when users try to use some unsupported features. This is incomplete.
  • DROP Index
  • Unsupported column type
  • Joins not supported with CTE
  • LOCKs not supported in general, CTE's as well
  • UPDATE with joins
  • ALTER table stuff has lots of unsupported behaviors
• Finish the "in" support tests
• Check I didn't miss any tests from the OLD connection test.
• Check the MYSQL tests to see if I have any others there that are relevant.

[warmwaffles]

Exciting.

[warmwaffles]

@jeregrine how's this coming along?

[ruslandoga]

Should Enum.map(hints, &[?\s | &1]), be removed from the iolist below?

[jeregrine]

good catch!

[jeregrine]

@warmwaffles I fixed the merge conflicts but integration tests will continue to fail until a new ecto version is cut with this in it elixir-ecto/ecto#4083

[warmwaffles]

Ah no problem then. Let's wait for them to cut a new version. There shouldn't be too many merge conflicts until then.

[jeregrine]

Are we ready to go? Or should we merge #107 instead?

[warmwaffles]

I want to give you all the credit for the work you did here. When I squash merge #107, it will consolidate under @fredwu's name.

What I can do is just bump to ecto 3.10, then you rebase this on top. Then @fredwu rebase his work after we merge your work @jeregrine.

How does that sound?

[warmwaffles]

Actually @jeregrine let me just squash merge this and @fredwu can just rebase on top.