Databases
StackOverflow2013
Postsdbo
PORails migrations for postgreSQL schemas
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails migrations for postgreSQL schemas
    primarykey
    data
    text
    <p>I'm working on a multi-tenant rails application using PostgreSQL schemas for different clients. Rails migrations don't work with multiple schemas out of the box, so I made the following rake task to migrate all schemas and it seems to work. My question is if others have implemented better and more elegant solutions. I would also be really happy with a good tutorial including rails code examples for PostgreSQL using multiple schemas. So far I have only found a good presentation on the subject <a href="http://aac2009.confreaks.com/06-feb-2009-14-30-writing-multi-tenant-applications-in-rails-guy-naor.html" rel="noreferrer">http://aac2009.confreaks.com/06-feb-2009-14-30-writing-multi-tenant-applications-in-rails-guy-naor.html</a> and an example of what I'm aiming for tomayko.com/writings/rails-multiple-connections</p> <pre><code>desc 'Migrates all postgres schemas' task :schemas do # get all schemas env = "#{RAILS_ENV}" config = YAML::load(File.open('config/database.yml')) ActiveRecord::Base.establish_connection(config[env]) schemas = ActiveRecord::Base.connection.select_values("select * from pg_namespace where nspname != 'information_schema' AND nspname NOT LIKE 'pg%'") puts "Migrate schemas: #{schemas.inspect}" # migrate each schema schemas.each do |schema| puts "Migrate schema: #{schema}" config = YAML::load(File.open('config/database.yml')) config[env]["schema_search_path"] = schema ActiveRecord::Base.establish_connection(config[env]) ActiveRecord::Base.logger = Logger.new(STDOUT) ActiveRecord::Migrator.migrate('db/migrate', ENV["VERSION"] ? ENV["VERSION"].to_i : nil) end end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBeatlevic
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails migrations for postgreSQL schemas
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails migrations for postgreSQL schemas
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails migrations for postgreSQL schemas
      1. This table or related slice is empty.
      1. VTUpMod
    1. COLiquibase does work with schemas as far as i know
      singulars
      1. PORails migrations for postgreSQL schemas
      1. USJanning
    2. CO@Janning Liquibase is not a solution that works with the ActiveRecord modle that rails uses.
      singulars
      1. PORails migrations for postgreSQL schemas
      1. USlillq
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload