Skip to content
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.

support mysql #163

Open
josephholsten opened this issue Jul 18, 2014 · 5 comments
Open

support mysql #163

josephholsten opened this issue Jul 18, 2014 · 5 comments

Comments

@josephholsten
Copy link

mysql doesn't support the constraint in https://github.com/obfuscurity/descartes/blob/master/lib/descartes/migrations/006_AddGraphDashboardRelationConstraints.rb.

Any thoughts on how I can add this constraint to the app code so we can keep the feature and support mysql as well?

@damm
Copy link

damm commented Jul 18, 2014

:o descartes supports mysql? I didn't see that.

@obfuscurity
Copy link
Owner

What about it doesn't work? MySQL supports multi-column unique constraints afaik.

@damm
Copy link

damm commented Jul 18, 2014

Well the Sequel gem should support mysql as well.

@obfuscurity
Copy link
Owner

Yeah, it does. That's why we need more info.

@josephholsten
Copy link
Author

Sequel works just fine, but MySQL doesn't like the index name that sequel uses to implement this constraint.

Further investigation showed me that MySQL supports compound unique constraints, so it's possible that this is a bug in sequel or that we're not passing enough info for it to choose a reasonable index name.

I'll dig in further.

On Jul 18, 2014, at 5:25, Jason Dixon [email protected] wrote:

Yeah, it does. That's why we need more info.


Reply to this email directly or view it on GitHub.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants