rails_sql_views4 0.0.1 → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 544ca00235098c24ee35405ec3e987b4f5ab6bcd
-  data.tar.gz: ee2305432c09bd0d162a5f1cd22604449074bc99
+  metadata.gz: 6c02f5c00bad55e5de74007d32ed14aa3aa8bb5a
+  data.tar.gz: 9a78a4c88903c846afb96a3a15a3cb19c3652be9
 SHA512:
-  metadata.gz: 628f2d45cc82e7ed647096a9a0f20748e4a82d7d5995c846bea5e3f7991ac4c7126d29e530d4e3806625d01a967d683e129fee8bb00e9f09420c0460343099aa
-  data.tar.gz: 69e04f6f5de2f4c7ae9186bb5e7b01e46da7c1bfafa052506a6412eab287534e1f355502f6d7d34a769495f1f0cd5c20f39705fddc672ba9021087fd07294202
+  metadata.gz: 435ff55234b6fbe9ae0bde92c0e414e5cd1eb2ba12b39439eb5832048beed7bedcd5fb5e17218b9dff6ffbcbda0c7b1d1312b23decd4aba5ea15211e2c9c22ca
+  data.tar.gz: eee216b8a5db4c4e073bf05289f72fb0552f53716c59f29d2e6c0aa8f7bfa21cfb8f2febc560202cf92abac5af200013675170737cba0b369631a172fbc26c6e

data/lib/rails_sql_views4/connection_adapters/abstract/schema_statements.rb

@@ -10,6 +10,14 @@ module RailsSqlViews4
       # [<tt>:check_option</tt>]
       #   Specify restrictions for inserts or updates in updatable views. ANSI SQL 92 defines two check option
       #   values: CASCADED and LOCAL. See your database documentation for allowed values.
+      #
+      #
+      # we have a problem with the force option in postgres
+      # rescue nil will rescue the ruby program, but we still have an error for postgres
+      # and unfortunatly for postgress, the first error will stop the interpretor : 
+      # ActiveRecord::StatementInvalid Exception: PG::InFailedSqlTransaction: ERROR:  
+      # current transaction is aborted, commands ignored until end of transaction block
+      #
       def create_view(name, select_query, options={})
         if supports_views?
           view_definition = ViewDefinition.new(self, select_query)
@@ -19,6 +27,7 @@ module RailsSqlViews4
           end
 
           if options[:force]
+            puts" TOTO : Please, force option is not correctly implemented in postgres"
             drop_view(name) rescue nil
           end
 
@@ -31,6 +40,7 @@ module RailsSqlViews4
           end
           create_sql << "AS #{view_definition.select_query}"
           create_sql << " WITH #{options[:check_option]} CHECK OPTION" if options[:check_option]
+          debugger;
           execute create_sql
         end
       end
@@ -74,7 +84,8 @@ module RailsSqlViews4
       #   Specify the drop behavior. ANSI SQL 92 defines two drop behaviors, CASCADE and RESTRICT. See your
       #   database documentation to determine what drop behaviors are available.
       def drop_view(name, options={})
-        if supports_views?
+        # if supports_views?  # because of postgres (see create_view with force option)
+        if supports_views? & table_exists?(name)
           drop_sql = "DROP VIEW #{quote_table_name(name)}"
           drop_sql << " #{options[:drop_behavior]}" if options[:drop_behavior]
           execute drop_sql

data/lib/rails_sql_views4/connection_adapters/postgresql_adapter.rb

@@ -20,6 +20,17 @@ module RailsSqlViews4
         query(q, name).map { |row| row[0] }
       end
       
+       def tables(name = nil) #:nodoc:
+          q = <<-SQL
+          SELECT table_name, table_type
+            FROM information_schema.tables
+           WHERE table_schema IN (#{schemas})
+             AND table_type = 'TABLE'
+          SQL
+
+          query(q, name).map { |row| row[0] }
+        end
+      
       def base_tables(name = nil)
         q = <<-SQL
         SELECT table_name, table_type
@@ -55,7 +66,7 @@ module RailsSqlViews4
         # TODO
         # puts in postgres adapter ??? not in SQLITE ?
         # select_value(q, name) or raise "No view called #{view} found"
-        select_value(q, name).gsub("CREATE VIEW #{view} AS ", "")) or raise "No view called #{view} found"
+        select_value(q, name).gsub("CREATE VIEW #{view} AS ", "") or raise "No view called #{view} found"
         
       end
 

data/lib/rails_sql_views4/version.rb

@@ -1,3 +1,3 @@
 module RailsSqlViews4
-  VERSION = "0.0.1"
+  VERSION = "0.0.2"
 end

data/test/adapter_test.rb

@@ -9,6 +9,7 @@ class AdapterTest < ActiveSupport::TestCase
   end
   
   def test_tables
+    debugger
     create_view
     found = ActiveRecord::Base.connection.tables.sort
     found.delete(ActiveRecord::Migrator.schema_migrations_table_name)

data/test/dummy/config/database.yml

@@ -5,20 +5,23 @@
 #   gem 'sqlite3'
 #
 default: &default
-  adapter: sqlite3
+  adapter: postgresql
   pool: 5
   timeout: 5000
 
 development:
-  <<: *default
-  database: db/development.sqlite3
+  adapter: postgresql
+  encoding: unicode
+  database: rails_sql_views4_development 
+
 
 # Warning: The database defined as "test" will be erased and
 # re-generated from your development database when you run "rake".
 # Do not set this db to the same as development or production.
 test:
-  <<: *default
-  database: db/test.sqlite3
+  adapter: postgresql
+  encoding: unicode
+  database: rails_sql_views_unittest
 
 production:
   <<: *default

data/test/dummy/db/schema.rb

@@ -13,6 +13,9 @@
 
 ActiveRecord::Schema.define(version: 20141228200440) do
 
+  # These are extensions that must be enabled in order to support this database
+  enable_extension "plpgsql"
+
   create_table "items", force: true do |t|
     t.integer  "person_id"
     t.datetime "created_at"

data/test/dummy/log/development.log

@@ -437,3 +437,248 @@ SQLite3::SQLException: no such view: v_people: DROP VIEW "v_people"
    (0.8ms)  DROP VIEW "v_people"
    (0.9ms)  CREATE VIEW "v_people" AS select id, first_name, last_name, ssn, address_id from people
    (0.1ms)  SELECT version FROM "schema_migrations"
+   (3.9ms)  CREATE TABLE "schema_migrations" ("version" character varying NOT NULL) 
+   (1.0ms)  CREATE UNIQUE INDEX  "unique_schema_migrations" ON "schema_migrations"  ("version")
+  ActiveRecord::SchemaMigration Load (0.2ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+Migrating to CreatePeople (20141228200436)
+   (0.1ms)  BEGIN
+   (3.1ms)  CREATE TABLE "people" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "address_id" integer) 
+  SQL (0.5ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200436"]]
+   (0.3ms)  COMMIT
+Migrating to CreatePeople2 (20141228200437)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200437_create_people2.rb:8)
+   (3.1ms)  CREATE TABLE "people2" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200437"]]
+   (0.4ms)  COMMIT
+Migrating to CreatePlaces (20141228200438)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200438_create_places.rb:9)
+   (3.3ms)  CREATE TABLE "places" ("id" serial primary key, "address" text, "city" character varying, "cstate" character varying, "country" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200438"]]
+   (0.5ms)  COMMIT
+Migrating to CreateItems (20141228200439)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200439_create_items.rb:5)
+   (1.6ms)  CREATE TABLE "items" ("id" serial primary key, "person_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200439"]]
+   (0.4ms)  COMMIT
+Migrating to CreateItemsPeople (20141228200440)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200440_create_items_people.rb:6)
+   (2.2ms)  CREATE TABLE "items_people" ("id" serial primary key, "person_id" integer, "item_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200440"]]
+   (0.3ms)  COMMIT
+  ActiveRecord::SchemaMigration Load (0.2ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+   (2.5ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'BASE TABLE'
+
+   (0.7ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'VIEW'
+
+   (2.5ms)  CREATE TABLE "schema_migrations" ("version" character varying NOT NULL) 
+   (0.9ms)  CREATE UNIQUE INDEX  "unique_schema_migrations" ON "schema_migrations"  ("version")
+  ActiveRecord::SchemaMigration Load (0.2ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+Migrating to CreatePeople (20141228200436)
+   (0.1ms)  BEGIN
+   (3.0ms)  CREATE TABLE "people" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "address_id" integer) 
+  SQL (0.3ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200436"]]
+   (0.4ms)  COMMIT
+Migrating to CreatePeople2 (20141228200437)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200437_create_people2.rb:8)
+   (2.2ms)  CREATE TABLE "people2" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200437"]]
+   (0.4ms)  COMMIT
+Migrating to CreatePlaces (20141228200438)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200438_create_places.rb:9)
+   (2.5ms)  CREATE TABLE "places" ("id" serial primary key, "address" text, "city" character varying, "cstate" character varying, "country" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200438"]]
+   (0.4ms)  COMMIT
+Migrating to CreateItems (20141228200439)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200439_create_items.rb:5)
+   (2.9ms)  CREATE TABLE "items" ("id" serial primary key, "person_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200439"]]
+   (0.3ms)  COMMIT
+Migrating to CreateItemsPeople (20141228200440)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200440_create_items_people.rb:6)
+   (1.7ms)  CREATE TABLE "items_people" ("id" serial primary key, "person_id" integer, "item_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200440"]]
+   (0.4ms)  COMMIT
+  ActiveRecord::SchemaMigration Load (0.3ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+   (2.6ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'BASE TABLE'
+
+   (0.6ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'VIEW'
+
+   (2.8ms)  CREATE TABLE "schema_migrations" ("version" character varying NOT NULL) 
+   (1.0ms)  CREATE UNIQUE INDEX  "unique_schema_migrations" ON "schema_migrations"  ("version")
+  ActiveRecord::SchemaMigration Load (0.2ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+Migrating to CreatePeople (20141228200436)
+   (0.1ms)  BEGIN
+   (2.7ms)  CREATE TABLE "people" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "address_id" integer) 
+  SQL (0.3ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200436"]]
+   (0.5ms)  COMMIT
+Migrating to CreatePeople2 (20141228200437)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200437_create_people2.rb:8)
+   (2.4ms)  CREATE TABLE "people2" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200437"]]
+   (1.3ms)  COMMIT
+Migrating to CreatePlaces (20141228200438)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200438_create_places.rb:9)
+   (2.1ms)  CREATE TABLE "places" ("id" serial primary key, "address" text, "city" character varying, "cstate" character varying, "country" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200438"]]
+   (0.3ms)  COMMIT
+Migrating to CreateItems (20141228200439)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200439_create_items.rb:5)
+   (2.5ms)  CREATE TABLE "items" ("id" serial primary key, "person_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200439"]]
+   (0.3ms)  COMMIT
+Migrating to CreateItemsPeople (20141228200440)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200440_create_items_people.rb:6)
+   (1.5ms)  CREATE TABLE "items_people" ("id" serial primary key, "person_id" integer, "item_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200440"]]
+   (0.4ms)  COMMIT
+  ActiveRecord::SchemaMigration Load (0.2ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+   (3.4ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'BASE TABLE'
+
+   (0.7ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'VIEW'
+
+   (2.5ms)  CREATE TABLE "schema_migrations" ("version" character varying NOT NULL) 
+   (0.9ms)  CREATE UNIQUE INDEX  "unique_schema_migrations" ON "schema_migrations"  ("version")
+  ActiveRecord::SchemaMigration Load (0.3ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+Migrating to CreatePeople (20141228200436)
+   (0.1ms)  BEGIN
+   (3.1ms)  CREATE TABLE "people" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "address_id" integer) 
+  SQL (0.3ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200436"]]
+   (0.4ms)  COMMIT
+Migrating to CreatePeople2 (20141228200437)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200437_create_people2.rb:8)
+   (2.4ms)  CREATE TABLE "people2" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200437"]]
+   (0.3ms)  COMMIT
+Migrating to CreatePlaces (20141228200438)
+   (0.5ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200438_create_places.rb:9)
+   (2.6ms)  CREATE TABLE "places" ("id" serial primary key, "address" text, "city" character varying, "cstate" character varying, "country" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200438"]]
+   (0.3ms)  COMMIT
+Migrating to CreateItems (20141228200439)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200439_create_items.rb:5)
+   (2.1ms)  CREATE TABLE "items" ("id" serial primary key, "person_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200439"]]
+   (0.3ms)  COMMIT
+Migrating to CreateItemsPeople (20141228200440)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200440_create_items_people.rb:6)
+   (1.5ms)  CREATE TABLE "items_people" ("id" serial primary key, "person_id" integer, "item_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.1ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200440"]]
+   (0.3ms)  COMMIT
+  ActiveRecord::SchemaMigration Load (0.3ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+   (2.7ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'BASE TABLE'
+
+   (0.7ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'VIEW'
+
+   (16.9ms)  CREATE TABLE "schema_migrations" ("version" character varying NOT NULL) 
+   (1.2ms)  CREATE UNIQUE INDEX  "unique_schema_migrations" ON "schema_migrations"  ("version")
+  ActiveRecord::SchemaMigration Load (0.3ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+Migrating to CreatePeople (20141228200436)
+   (0.1ms)  BEGIN
+   (2.9ms)  CREATE TABLE "people" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "address_id" integer) 
+  SQL (0.6ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200436"]]
+   (0.8ms)  COMMIT
+Migrating to CreatePeople2 (20141228200437)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200437_create_people2.rb:8)
+   (2.5ms)  CREATE TABLE "people2" ("id" serial primary key, "first_name" character varying, "last_name" character varying, "ssn" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200437"]]
+   (0.5ms)  COMMIT
+Migrating to CreatePlaces (20141228200438)
+   (0.2ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200438_create_places.rb:9)
+   (2.5ms)  CREATE TABLE "places" ("id" serial primary key, "address" text, "city" character varying, "cstate" character varying, "country" character varying, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200438"]]
+   (0.4ms)  COMMIT
+Migrating to CreateItems (20141228200439)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200439_create_items.rb:5)
+   (2.0ms)  CREATE TABLE "items" ("id" serial primary key, "person_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200439"]]
+   (0.4ms)  COMMIT
+Migrating to CreateItemsPeople (20141228200440)
+   (0.3ms)  BEGIN
+DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/laurent/Desktop/code/rails_sql_views4/test/dummy/db/migrate/20141228200440_create_items_people.rb:6)
+   (2.2ms)  CREATE TABLE "items_people" ("id" serial primary key, "person_id" integer, "item_id" integer, "created_at" timestamp, "updated_at" timestamp) 
+  SQL (0.2ms)  INSERT INTO "schema_migrations" ("version") VALUES ($1)  [["version", "20141228200440"]]
+   (0.3ms)  COMMIT
+  ActiveRecord::SchemaMigration Load (0.2ms)  SELECT "schema_migrations".* FROM "schema_migrations"
+   (5.5ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'BASE TABLE'
+
+   (0.8ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type = 'VIEW'
+
+   (0.3ms)  DROP VIEW "v_people"
+PG::UndefinedTable: ERROR:  view "v_people" does not exist
+: DROP VIEW "v_people"
+   (2.4ms)  CREATE VIEW "v_people" AS select first_name, last_name, ssn from people
+   (4.2ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type IN ('BASE TABLE', 'VIEW')
+
+  Person Load (0.5ms)  SELECT "people".* FROM "people"
+   (4.0ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type IN ('BASE TABLE', 'VIEW')
+
+   (0.2ms)  BEGIN
+  SQL (0.7ms)  INSERT INTO "people" ("first_name", "last_name") VALUES ($1, $2) RETURNING "id"  [["first_name", "Laurent"], ["last_name", "Buffat"]]
+   (0.4ms)  COMMIT
+   (0.2ms)  BEGIN
+  SQL (0.5ms)  INSERT INTO "people" ("last_name", "first_name") VALUES ($1, $2) RETURNING "id"  [["last_name", "Villemagne"], ["first_name", "Genevieve"]]
+   (1.0ms)  COMMIT
+  Person Load (0.4ms)  SELECT "people".* FROM "people"
+   (2.2ms)          SELECT table_name, table_type
+          FROM information_schema.tables
+         WHERE table_schema IN ('"$user"','public')
+           AND table_type IN ('BASE TABLE', 'VIEW')
+
+  Person Load (0.7ms)  SELECT  "people".* FROM "people"  ORDER BY "people"."id" ASC LIMIT 1
+  VPerson Load (0.9ms)  SELECT  "v_people".* FROM "v_people" LIMIT 1
+  Person Load (0.5ms)  SELECT  "people".* FROM "people"  ORDER BY "people"."id" ASC LIMIT 1