tern 0.6.0

data/lib/tern/generators/change.sql

@@ -0,0 +1,4 @@
+
+
+---- CREATE above / DROP below ----
+

data/lib/tern/generators/new/alterations/001_create_people.sql.example

@@ -0,0 +1,16 @@
+Sequel.migration do
+  up do
+    run <<-END_SQL
+      CREATE TABLE people(
+        id serial PRIMARY KEY,
+        name varchar NOT NULL
+      );
+    END_SQL
+  end
+
+  down do
+    run <<-END_SQL
+      DROP TABLE people;
+    END_SQL
+  end
+end

data/lib/tern/generators/new/config.yml.tt

@@ -0,0 +1,15 @@
+alterations:
+  table: tern_alterations
+  column: version
+definitions:
+  table: tern_definitions
+environments:
+  development:
+    adapter: postgres
+    database: <%= app_name %>_development
+  test:
+    adapter: postgres
+    database: <%= app_name %>_test
+  production:
+    adapter: postgres
+    database: <%= app_name %>_production

data/lib/tern/generators/new/definitions/sequence.yml

@@ -0,0 +1,18 @@
+# Put the relative path to your definition files in the sequence they should run.
+#
+# Most definitions should go in the default list. These will be dropped and
+# recreated every migration.
+#
+# Definitions that should not automatically be dropped and created can be put in
+# different lists. This is useful for definitions that make take prohibitively
+# to drop and create every migration such as check constraints.
+#
+# Run alternative sequences by specifying sequences in order to migrate command.
+# Example: rake migrate sequences=expensive,default
+#
+# default:
+#   - ultimate_answer.sql
+# expensive:
+#   - super_slow_check_constraint.sql
+
+default: []

data/lib/tern/generators/new/definitions/ultimate_answer.sql.example

@@ -0,0 +1,7 @@
+CREATE FUNCTION ultimate_answer() RETURNS integer AS $$
+  SELECT 42;
+$$ LANGUAGE SQL;
+
+---- CREATE above / DROP below ----
+
+DROP FUNCTION ultimate_answer();

data/spec/projects/alterations/alterations/001_create_people.sql

@@ -0,0 +1,8 @@
+CREATE TABLE people(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE people;

data/spec/projects/alterations/alterations/002_create_animals.sql

@@ -0,0 +1,8 @@
+CREATE TABLE animals(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE animals;

data/spec/projects/alterations/alterations/003_create_plants.sql

@@ -0,0 +1,8 @@
+CREATE TABLE plants(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE plants;

data/spec/projects/alterations/config.yml

@@ -0,0 +1,15 @@
+alterations:
+  table: tern_alterations
+  column: version
+definitions:
+  table: tern_definitions
+environments:
+  development:
+    adapter: postgres
+    database: tern_test_development
+  test:
+    adapter: postgres
+    database: tern_test_test
+  production:
+    adapter: postgres
+    database: tern_test_production

data/spec/projects/alterations/definitions/sequence.yml

@@ -0,0 +1,18 @@
+# Put the relative path to your definition files in the sequence they should run.
+#
+# Most definitions should go in the default list. These will be dropped and
+# recreated every migration.
+#
+# Definitions that should not automatically be dropped and created can be put in
+# different lists. This is useful for definitions that make take prohibitively
+# to drop and create every migration such as check constraints.
+#
+# Run alternative sequences by specifying sequences in order to migrate command.
+# Example: rake migrate sequences=expensive,default
+#
+# default:
+#   - ultimate_answer.sql
+# expensive:
+#   - super_slow_check_constraint.sql
+
+default: []

data/spec/projects/alterations/definitions/ultimate_answer.sql.example

@@ -0,0 +1,7 @@
+CREATE FUNCTION ultimate_answer() RETURNS integer AS $$
+  SELECT 42;
+$$ LANGUAGE SQL;
+
+---- CREATE above / DROP below ----
+
+DROP FUNCTION ultimate_answer();

data/spec/projects/definitions/alterations/001_create_people.sql.example

@@ -0,0 +1,16 @@
+Sequel.migration do
+  up do
+    run <<-END_SQL
+      CREATE TABLE people(
+        id serial PRIMARY KEY,
+        name varchar NOT NULL
+      );
+    END_SQL
+  end
+
+  down do
+    run <<-END_SQL
+      DROP TABLE people;
+    END_SQL
+  end
+end

data/spec/projects/definitions/config.yml

@@ -0,0 +1,15 @@
+alterations:
+  table: tern_alterations
+  column: version
+definitions:
+  table: tern_definitions
+environments:
+  development:
+    adapter: postgres
+    database: tern_test_development
+  test:
+    adapter: postgres
+    database: tern_test_test
+  production:
+    adapter: postgres
+    database: tern_test_production

data/spec/projects/definitions/definitions/sequence.yml

@@ -0,0 +1,19 @@
+# Put the relative path to your definition files in the sequence they should run.
+#
+# Most definitions should go in the default list. These will be dropped and
+# recreated every migration.
+#
+# Definitions that should not automatically be dropped and created can be put in
+# different lists. This is useful for definitions that make take prohibitively
+# to drop and create every migration such as check constraints.
+#
+# Run alternative sequences by specifying sequences in order to migrate command.
+# Example: rake migrate sequences=expensive,default
+#
+# default:
+#   - ultimate_answer.sql
+# expensive:
+#   - super_slow_check_constraint.sql
+
+default:
+  - ultimate_answer.sql

data/spec/projects/definitions/definitions/ultimate_answer.sql

@@ -0,0 +1,7 @@
+CREATE FUNCTION ultimate_answer() RETURNS integer AS $$
+  SELECT 42;
+$$ LANGUAGE SQL;
+
+---- CREATE above / DROP below ----
+
+DROP FUNCTION ultimate_answer();

data/spec/projects/dependencies_1/alterations/001_create_widgets.sql

@@ -0,0 +1,9 @@
+CREATE TABLE widgets(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL,
+  weight integer NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE widgets;

data/spec/projects/dependencies_1/config.yml

@@ -0,0 +1,15 @@
+alterations:
+  table: tern_alterations
+  column: version
+definitions:
+  table: tern_definitions
+environments:
+  development:
+    adapter: postgres
+    database: tern_test_development
+  test:
+    adapter: postgres
+    database: tern_test_test
+  production:
+    adapter: postgres
+    database: tern_test_production

data/spec/projects/dependencies_1/definitions/sequence.yml

@@ -0,0 +1,19 @@
+# Put the relative path to your definition files in the sequence they should run.
+#
+# Most definitions should go in the default list. These will be dropped and
+# recreated every migration.
+#
+# Definitions that should not automatically be dropped and created can be put in
+# different lists. This is useful for definitions that make take prohibitively
+# to drop and create every migration such as check constraints.
+#
+# Run alternative sequences by specifying sequences in order to migrate command.
+# Example: rake migrate sequences=expensive,default
+#
+# default:
+#   - ultimate_answer.sql
+# expensive:
+#   - super_slow_check_constraint.sql
+
+default:
+  - widgets_view.sql

data/spec/projects/dependencies_1/definitions/ultimate_answer.sql.example

@@ -0,0 +1,7 @@
+CREATE FUNCTION ultimate_answer() RETURNS integer AS $$
+  SELECT 42;
+$$ LANGUAGE SQL;
+
+---- CREATE above / DROP below ----
+
+DROP FUNCTION ultimate_answer();

data/spec/projects/dependencies_1/definitions/widgets_view.sql

@@ -0,0 +1,5 @@
+CREATE VIEW widgets_view AS SELECT * FROM widgets;
+
+---- CREATE above / DROP below ----
+
+DROP VIEW widgets_view;

data/spec/projects/dependencies_2/alterations/001_create_widgets.sql

@@ -0,0 +1,9 @@
+CREATE TABLE widgets(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL,
+  weight integer NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE widgets;

data/spec/projects/dependencies_2/config.yml

@@ -0,0 +1,15 @@
+alterations:
+  table: tern_alterations
+  column: version
+definitions:
+  table: tern_definitions
+environments:
+  development:
+    adapter: postgres
+    database: tern_test_development
+  test:
+    adapter: postgres
+    database: tern_test_test
+  production:
+    adapter: postgres
+    database: tern_test_production

data/spec/projects/dependencies_2/definitions/sequence.yml

@@ -0,0 +1,18 @@
+# Put the relative path to your definition files in the sequence they should run.
+#
+# Most definitions should go in the default list. These will be dropped and
+# recreated every migration.
+#
+# Definitions that should not automatically be dropped and created can be put in
+# different lists. This is useful for definitions that make take prohibitively
+# to drop and create every migration such as check constraints.
+#
+# Run alternative sequences by specifying sequences in order to migrate command.
+# Example: rake migrate sequences=expensive,default
+#
+# default:
+#   - ultimate_answer.sql
+# expensive:
+#   - super_slow_check_constraint.sql
+
+default: []

data/spec/projects/dependencies_2/definitions/ultimate_answer.sql.example

@@ -0,0 +1,7 @@
+CREATE FUNCTION ultimate_answer() RETURNS integer AS $$
+  SELECT 42;
+$$ LANGUAGE SQL;
+
+---- CREATE above / DROP below ----
+
+DROP FUNCTION ultimate_answer();

data/spec/projects/duplicated_alteration/alterations/001_create_people.sql

@@ -0,0 +1,8 @@
+CREATE TABLE people(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE people;

data/spec/projects/duplicated_alteration/alterations/002_create_animals.sql

@@ -0,0 +1,8 @@
+CREATE TABLE animals(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE animals;

data/spec/projects/duplicated_alteration/alterations/002_create_plants.sql

@@ -0,0 +1,8 @@
+CREATE TABLE plants(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE plants;

data/spec/projects/duplicated_alteration/config.yml

@@ -0,0 +1,15 @@
+alterations:
+  table: tern_alterations
+  column: version
+definitions:
+  table: tern_definitions
+environments:
+  development:
+    adapter: postgres
+    database: tern_test_development
+  test:
+    adapter: postgres
+    database: tern_test_test
+  production:
+    adapter: postgres
+    database: tern_test_production

data/spec/projects/duplicated_alteration/definitions/sequence.yml

@@ -0,0 +1,18 @@
+# Put the relative path to your definition files in the sequence they should run.
+#
+# Most definitions should go in the default list. These will be dropped and
+# recreated every migration.
+#
+# Definitions that should not automatically be dropped and created can be put in
+# different lists. This is useful for definitions that make take prohibitively
+# to drop and create every migration such as check constraints.
+#
+# Run alternative sequences by specifying sequences in order to migrate command.
+# Example: rake migrate sequences=expensive,default
+#
+# default:
+#   - ultimate_answer.sql
+# expensive:
+#   - super_slow_check_constraint.sql
+
+default: []

data/spec/projects/duplicated_alteration/definitions/ultimate_answer.sql.example

@@ -0,0 +1,7 @@
+CREATE FUNCTION ultimate_answer() RETURNS integer AS $$
+  SELECT 42;
+$$ LANGUAGE SQL;
+
+---- CREATE above / DROP below ----
+
+DROP FUNCTION ultimate_answer();

data/spec/projects/irreversible_alterations/alterations/001_create_people.sql

@@ -0,0 +1,8 @@
+CREATE TABLE people(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE people;

data/spec/projects/irreversible_alterations/alterations/002_create_animals.sql

@@ -0,0 +1,4 @@
+CREATE TABLE animals(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);

data/spec/projects/irreversible_alterations/alterations/003_create_plants.sql

@@ -0,0 +1,8 @@
+CREATE TABLE plants(
+  id serial PRIMARY KEY,
+  name varchar NOT NULL
+);
+
+---- CREATE above / DROP below ----
+
+DROP TABLE plants;

data/spec/projects/irreversible_alterations/config.yml

@@ -0,0 +1,15 @@
+alterations:
+  table: tern_alterations
+  column: version
+definitions:
+  table: tern_definitions
+environments:
+  development:
+    adapter: postgres
+    database: tern_test_development
+  test:
+    adapter: postgres
+    database: tern_test_test
+  production:
+    adapter: postgres
+    database: tern_test_production