[opensuse-web] OSEM + PostgreSQL
OSEM, We at Command Prompt have ported OSEM to work with PostgreSQL. https://github.com/commandprompt/osem-pg I have a running instance and everything seems to work. I am currently evaluating it for PgConfUS and we of course could not use another database technology other than PostgreSQL. Cheers! JD -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. Everyone appreciates your honesty, until you are honest with them. Unless otherwise stated, opinions are my own. -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
On vendredi, 9 décembre 2016 10.51:27 h CET Joshua D. Drake wrote:
OSEM,
We at Command Prompt have ported OSEM to work with PostgreSQL.
https://github.com/commandprompt/osem-pg
I have a running instance and everything seems to work. I am currently evaluating it for PgConfUS and we of course could not use another database technology other than PostgreSQL.
Cheers!
JD
Wouah, thanks for the report, Joshua. Hope the port can be merged upstream, and the product met your expectation. It's always good when the tools we create for all, are then use by all. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship Blue elephant in heart GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Hi Joshua, it's great to hear that you are considering it for PgConf :) I think we had a request about postgresql in the past. Did you stumble upon any code that needed to be amended? And what about the migration during the setup? Did that go smoothly as well? We would love to receive a PR. Please do share more of your experience! You can find us here on the ML, on IRC freenode server #osem and of course github. Stella
On 12/09/2016 01:01 PM, Stella Rouzi (differentreality) wrote:
Hi Joshua,
it's great to hear that you are considering it for PgConf :)
I think we had a request about postgresql in the past. Did you stumble upon any code that needed to be amended?
Some but not much. I will get more details. I know there was some errors in your model (you have a join going from UUID to int(16)) that won't work in Pg because we don't have implicit casting (all kinds of ugliness happens with implicit casting).
And what about the migration during the setup? Did that go smoothly as well? We would love to receive a PR.
Already sent out on the @postgresql twitter (10k followers).
Please do share more of your experience! You can find us here on the ML, on IRC freenode server #osem and of course github.
JD -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. Everyone appreciates your honesty, until you are honest with them. Unless otherwise stated, opinions are my own. -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
On 12/09/2016 01:01 PM, Stella Rouzi (differentreality) wrote:
Hi Joshua,
it's great to hear that you are considering it for PgConf :)
I think we had a request about postgresql in the past. Did you stumble upon any code that needed to be amended? And what about the migration during the setup? Did that go smoothly as well? We would love to receive a PR.
Please do share more of your experience! You can find us here on the ML, on IRC freenode server #osem and of course github.
This is the list of things we had to change to make the system work with postgresql: 1 fix database migrations to use the correct _boolean_ type of default values for boolean columns (0 -> false) commit c7cc8f8f34090baa1641013af8c3c6aa168052e9 2 conditionally use the add_monetize column instead of add_money for the ticket price DB migration; commit 06d8f6d3685e60042fa06458626e5e69c87d66aa 3 add missing columns to the ActiveRecord DB query so Postgres does not complain about the missing columns in GROUP By statements; commit 02cdf05b5d77d7878681029e5c9ba491e27f0908 4 add .count(:all) ActiveRecord call to force inclusion of the "count_all" column in query result set in queries which referred to this column (this happens automatically for other DBs, but not for Postgres); commit 02cdf05b5d77d7878681029e5c9ba491e27f0908 5 add UUID monkey patch to solve this ActiveUUID issue https://github.com/jashmenn/activeuuid/issues/74; commit a799ea7ca9cbf53eb6058bf636cf289694d16572 6 add PG database driver gem into the project's Gemfile; commit 78824559136b2c8424a44cae1a9d084ada8b212c 7 add updated schema.rb to the project source tree; commit 8903d88ef9cce38c50443d20008fad76ec65968b 8 fix the column types for ahoy_events.visit_id to use INTEGER instead of BINARY(16), so it matches with the FK type on the visits table (this has nothing to do with Postgres, just a bug I've spotted in the process); commit 5e7d5d60d838e28b4e731568ff43349338849a46 All changes were done to the master branch of the original OSEM.io source tree.
Stella
-- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. Everyone appreciates your honesty, until you are honest with them. -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Hey Joshua, I saw you sent a PR, it is much appreciated! We'll go over it and comment there. Thank you :) Stella On Tue, Dec 13, 2016 at 8:03 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
On 12/09/2016 01:01 PM, Stella Rouzi (differentreality) wrote:
Hi Joshua,
it's great to hear that you are considering it for PgConf :)
I think we had a request about postgresql in the past. Did you stumble upon any code that needed to be amended? And what about the migration during the setup? Did that go smoothly as well? We would love to receive a PR.
Please do share more of your experience! You can find us here on the ML, on IRC freenode server #osem and of course github.
This is the list of things we had to change to make the system work with postgresql:
1 fix database migrations to use the correct _boolean_ type of default values for boolean columns (0 -> false) commit c7cc8f8f34090baa1641013af8c3c6aa168052e9
2 conditionally use the add_monetize column instead of add_money for the ticket price DB migration; commit 06d8f6d3685e60042fa06458626e5e69c87d66aa
3 add missing columns to the ActiveRecord DB query so Postgres does not complain about the missing columns in GROUP By statements; commit 02cdf05b5d77d7878681029e5c9ba491e27f0908
4 add .count(:all) ActiveRecord call to force inclusion of the "count_all" column in query result set in queries which referred to this column (this happens automatically for other DBs, but not for Postgres); commit 02cdf05b5d77d7878681029e5c9ba491e27f0908
5 add UUID monkey patch to solve this ActiveUUID issue https://github.com/jashmenn/activeuuid/issues/74; commit a799ea7ca9cbf53eb6058bf636cf289694d16572
6 add PG database driver gem into the project's Gemfile; commit 78824559136b2c8424a44cae1a9d084ada8b212c
7 add updated schema.rb to the project source tree; commit 8903d88ef9cce38c50443d20008fad76ec65968b
8 fix the column types for ahoy_events.visit_id to use INTEGER instead of BINARY(16), so it matches with the FK type on the visits table (this has nothing to do with Postgres, just a bug I've spotted in the process); commit 5e7d5d60d838e28b4e731568ff43349338849a46
All changes were done to the master branch of the original OSEM.io source tree.
Stella
-- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. Everyone appreciates your honesty, until you are honest with them.
participants (3)
-
Bruno Friedmann -
Joshua D. Drake -
Stella Rouzi (differentreality)