#RubyOnRails - 27 January 2019
« Back 1 day Forward 1 day »
[00:20:16] zandimna: hello, has anyone successfully used ruby 2.6 for rails? I just installed a manjaro on a virtualbox and the rails on there returned the same error as i had on my arch.
[01:11:41] Zabot: What's the preferred way to run migrations against a production db? I know I can run rake:schema:load etc, but I don't want to give the rails db user create/delete access, much less the superuser access I would need to enable some postgres extensions.
[14:04:11] nakuku: Does it make sense to check subscription status on every request? (single query) Or set user status to 'subscribed' in database and make a job that runs once a day that checks if subscription ended?
[14:06:40] nakuku: Get it. So simpler = better in this case. At least it stateless, less error-prone and won't really affect performance, right?
[14:07:32] mikecmpbll: simpler is almost always better. you gotta have a pretty compelling case to do something more complex, and the performance of checking a date on each request isn't really compelling.
[14:08:11] mikecmpbll: if performance really was a concern, a cache would be better than introducing an aync process anyway.
[17:12:23] Pupeno: I'm converting a project from MySQL to PostgreSQL. After configuring it, I get the error: ActiveRecord::ConnectionTimeoutError: could not obtain a connection from the pool within 5.000 seconds (waited 5.000 seconds); all pooled connections were in use. I tried increasing the pool to 50. Another rails project on the same machine uses postgresql just fine. Any ideas what might be going ?
[17:34:24] Pupeno: havenwood: this is happening during rake db:migrate or rake db:create, so, I'm not sure the web server would have any effect, would it?
[17:38:50] havenwood: Pupeno: I wonder if it's related to that ^ issue, which was fixed in Rails 5.2.
[17:39:53] havenwood: https://github.com/rails/rails/pull/28057/files#diff-18d566ee525de376b1a3741881545631R173
[17:40:08] mikecmpbll: you've got something pretty weird going on if you can't load your rails environment without without exhausting the connection pool
[23:33:11] Zabot: Is there a way to generate a SQL script from a migration without actually running against a db?