This repository has been archived by the owner on Jan 28, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 110
Document major limitations #872
Comments
We've got an active fork with ~400 extra commits of bug fixes and additions after src-d quit. We're planning on continuing development indefinitely, as this is powering our open-source database product. Check it out if you're interested: https://github.com/liquidata-inc/go-mysql-server We haven't fixed concurrency issues (haven't used the server extensively enough to discover them on our own). If you have a repro we would be glad to look into it! Auto increment and bindvar support are both on our roadmap. |
Thanks for the tip zachmu! I'll definitely give it a shot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is an exciting project and I used it in my test harness for months, till the limitations basically made the situation untenable. At the very least I hope this issue helps people know what this project can and cannot do before they invest a lot of time in it.
Dead?
Sadly, I think all of src-d have stopped pushing to the open source repos. At best they have decided to invest in internal stuff. At worst the company went under six months ago. Keep this in mind along with the other limitations here.
Inscrutable errors
When you accidentally hit an unsupported feature, next steps are super difficult. Here's some code that I'd expect to error due to an unknown table for example:
The actual error is:
Again, keep this in mind for some of the unsupported features below.
Poor Concurrency support
The server seems to not support concurrent access very well, choking with inscrutable errors like the above on code that works non-concurrently. This is maybe not a big deal for many, but we tend to run all of our tests with
t.Parallel()
to shake out concurrency related bugs.No Auto incrementing value support
You basically cannot use SQL to insert into the database, instead you are forced to use
sql.Inserter
. This dramatically reduces the usefulness of this project.No Bindvar Support
If you try to use bind vars (?'s in SQL) this thing will choke on them, so you have to do that client side. This is livable since you can set that flag on the database connection.
I'm sure there's more, but all the above forced me to stop using this. I hope that the community can help pick this back up and give it the love it needs. I would love to pitch in and might, but I assume someone will need to fork it and give it a new home.
The text was updated successfully, but these errors were encountered: