New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL support in 0.x #31

Closed
e-oz opened this Issue Nov 29, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@e-oz

e-oz commented Nov 29, 2015

I've read you are going to add support of other databases only after 1.0, but differences between Postgre and MySQL are not so big, so please consider to support MySQL in 0.x. Then it will be well-tested for 1.0 :)

@sgrif

This comment has been minimized.

Member

sgrif commented Nov 29, 2015

I've updated my post to be less specific about the timeline for supporting other databases. It definitely makes sense to do pre-1.0 if possible, as it's unlikely to be something I can add without some amount of breaking API changes. However, I don't want to commit to any specific timeline.

I'm going to close this, as I've take the only actionable response to this I can.

As a side-note, since I haven't documented this anywhere, when we support MySQL, we'll still be following Postgres' semantics for a "correct query". So mixing aggregate and non-aggregate expressions will fail to compile, as will comparing a string with an integer (AKA please dump my database), etc.

@sgrif sgrif closed this Nov 29, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment