-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Postgres support #991
Postgres support #991
Conversation
…lt in the wounds.
What do you mean "on delete insertions"? Postgres supports triggers which let you do some pretty fancy stuff. |
Probably, but I didn't really have time to figure out the various UPSERT syntaxes ;) Someone who's a bit more of a postgres wizz will be able to make this much better I'm sure! But hopefully this is a useful starting point ... |
ah, I see MySQL's it looks like the recommended way to make atomic upserts in older versions is with PLSQL and an exception handler, yuck. http://www.postgresql.org/docs/current/static/plpgsql-control-structures.html#PLPGSQL-UPSERT-EXAMPLE |
Yeah or just do it in code to avoid the problem. As soon as you start relying on the database for fancy tricks like "on duplicate key update" you're going to be less portable. |
Yeah, that is what @mapkyca did |
Closes #76
This is very much experimental, because Postgres was giving me a headache, but I'm like a dog with a bone with this sort of thing ;)
Things not working quite yet: