Hi, I'd like to get some advice on how to properly handle connections in my application.
We're deploying a multi-tenant(-like) strategy using PG schemas. Basically we do that by setting the search_path properly on a before filter. Our application is composed by a Grails one and a Rails one (running Sequel) and I use the same approach in both. But "set search_path to xxx" will only take effect for that particular connection. For Grails this is a non-issue as long as I don't request a new Hibernate session (which I don't) since it will keep the same connection for all queries to the database. For the Rails app this is currently not an issue since I'm deploying it using Unicorn (multi-process approach). But I'd like to be able to change it to a threaded-based approach (like Puma or JRuby) if I want to and currently I can't because I wouldn't have any guarantees that the connection with the proper search_path set in the before filter will be the same next time I query the database from a controller for instance. So, I'd like to ask for any advices on how I could ensure I'll always use the same connection throughout the entire request cycle (using a pool of connections, of course)... Any ideas? Thanks in advance! -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/Hy5gmS1EU2UJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
