PostgreSQL support

[woahdae]

Nice project!!!

I messed around with how the tests run if you hack it to run postgres and copy/paste the tests here

This probably isn't news, but the higher-level interface tests pass, and the lower-level migration tests that assert statements fail, but entirely due to quotation differences between postgresql and mysql. That isn't to say the migrations would work, necessarily, since the tests just assert the sql output, but postgres doesn't vary that wildly.

I was hoping to get out of copy/paste land and see what could be extracted to test adapters generically, but kept running in to little issues asserting the quote style, or lack of quotes in some cases.

I'm out of time for now, but maybe this moves the ball a bit.

Thanks for the great idea!

[barunio]

Hi there -- thanks for the interest.

The main difference is that Postgres triggers are pretty different than MySQL's. With Postgres, you have to define a procedure and call that from the trigger. In MySQL, you can put the relevant logic in the trigger statement itself (which is what is done here).

I have a branch on my machine where I have some working prototype code to support Postgres. I'm pretty interested in getting that working, since this is one of the only things still keeping us tied to MySQL for our main database at WegoWise. I'd probably need a day or two to get the prototype to production-ready code. I'm hoping to have some time before the new year. If not, it'll be soon thereafter.

[woahdae]

Cool! I'll look forward to that.

On Wednesday, December 9, 2015, Barun Singh notifications@github.com
wrote:

Hi there -- thanks for the interest.

The main difference is that Postgres triggers are pretty different than
MySQL's. With Postgres, you have to define a procedure and call that from
the trigger. In MySQL, you can put the relevant logic in the trigger
statement itself (which is what is done here
https://github.com/wegowise/polymorpheus/blob/master/lib/polymorpheus/mysql_adapter.rb#L127-L136
).

I have a branch on my machine where I have some working prototype code to
support Postgres. I'm pretty interested in getting that working, since this
is one of the only things still keeping us tied to MySQL for our main
database at WegoWise. I'd probably need a day or two to get the prototype
to production-ready code. I'm hoping to have some time before the new year.
If not, it'll be soon thereafter.

—
Reply to this email directly or view it on GitHub
#21 (comment)
.

Sent from my phone

[oyeanuj]

@barunio Thank you for making this gem! Did the Postgres branch prototype ever get merged?