Rails Ruby on Rails

Comments and changes to this ticket

• You flagged this item as spam.
  

  nhatmy March 22nd, 2011 @ 07:46 AM

  giao xu quy de
  nha tho quy de
  nha tho nam dinh

• You flagged this item as spam.
  

  Juan Manuel Cuello April 21st, 2011 @ 09:07 PM

  It is easy to reproduce the problem. These are the steps:

  Create a Rails application that uses postgresql:

  $ rails new postgres_clone -d postgresql
  $ cd postgres_clone
  

  Then create a migration:

  #db/migrate/20110421194621_my_migration.rb
  class MyMigration < ActiveRecord::Migration
    def self.up
      connection.execute 'CREATE SCHEMA z_schema;'
      connection.execute 'CREATE TABLE z_schema.table1 (id integer, name varchar[255]);'
      connection.execute 'CREATE UNIQUE INDEX unique_table1_name ON z_schema.table1 USING btree (name);'
    end
  end
  

  And the run:
  

  $ rake db:create
  $ rake db:migrate
  $ rake db:test:clone_structure
  

  (in /home/juan/projects/postgres_clone)
  psql:/home/juan/projects/postgres_clone/db/development_structure.sql:75: ERROR:  relation "schema_migrations" does not exist
  LÍNEA 1: INSERT INTO schema_migrations (version) VALUES ('20110421194...
                       ^
  

• You flagged this item as spam.
  

  Juan Manuel Cuello May 13th, 2011 @ 09:39 PM

  The first patch I attached does not apply anymore because 'databases.rake' changed.
  

  This is the same patch but created recently from 'master'.

  • postgres-clone-structure-patch.diff 2 KB