db_fuel 1.1.0.pre.alpha.1 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0d7fce3d73ed5e5c1cfabfe4a578cd00fc6e932c7b32d1f60a7e17968163b247
-  data.tar.gz: 88eab379caeac681a34a8d58cc5ea3d8de51d242638d7707d4938d00a99f490d
+  metadata.gz: 7e2fc7d0ced8034053e409df7d34fa7127e21e357454221ad0262a59cc5bf2be
+  data.tar.gz: 6b2ce0fd3f4b6661f84820bb2394e49e1e11b111d3df02ce7981996b1eae386e
 SHA512:
-  metadata.gz: 91b4c18f3a081c296b005bbd6717f81d9595323dee3c69b7fca1594e4dfdf8063aba2052d54d6182bfa1a1440e3e8150117213961c4c92c010e7637ebb0f1560
-  data.tar.gz: b6e18bc0c58d6472465fe51fe06669bc54cb456526c6af1944de4c66b2e3e59281cf3ea21fbb54a78b9109e186536342b32dd2b15fc4561edc4ce4cc38abbe9b
+  metadata.gz: 73019f998b6db2d10d397e017ab5764dae1e7f4c42ceac403c0a345d91d21fe9da680a46a512a7dad0de85e0a731d6b81bffa0bfab85e7d9b6ca4912c571f0b0
+  data.tar.gz: f0e9b1e9dc28d29659c8532ef39229a8fa7e13c37f2476a75b37dbb62a46469e96ba6916a3eb0df1cc7cdb392c63031271443c0ab54d6933b8c7985f3fcb871b

data/CHANGELOG.md

@@ -1,4 +1,4 @@
-# 1.1.0 (TBD)
+# 1.1.0 (Decmeber 1st, 2020)
 
 New Jobs:
 

data/README.md

@@ -24,8 +24,8 @@ Refer to the [Burner](https://github.com/bluemarblepayroll/burner) library for m
 
 ### ActiveRecord Jobs
 
-* **db_fuel/active_record/find_or_insert** [table_name, attributes, debug, primary_key, register, separator, timestamps, unique_attributes]: An extension of the `db_fuel/active_record/insert` job that adds an existence check before sql insertion. The  `unique_attributes` will be converted to WHERE clauses for performing the existence check.
-* **db_fuel/active_record/insert** [table_name, attributes, debug, primary_key, register, separator, timestamps]: This job can take the objects in a register and insert them into a database table.  Attributes defines which object properties to convert to SQL.  Refer to the class and constructor specification for more detail.
+* **db_fuel/active_record/find_or_insert** [table_name, attributes, debug, primary_key, register, separator, timestamps, unique_attributes]: An extension of the `db_fuel/active_record/insert` job that adds an existence check before SQL insertion. The  `unique_attributes` will be converted to WHERE clauses for performing the existence check.
+* **db_fuel/active_record/insert** [table_name, attributes, debug, primary_key, register, separator, timestamps]: This job can take the objects in a register and insert them into a database table.  If primary_key is specified then its key will be set to the primary key.  Note that composite primary keys are not supported.  Attributes defines which object properties to convert to SQL.  Refer to the class and constructor specification for more detail.
 * **db_fuel/active_record/update** [table_name, attributes, debug, register, separator, timestamps, unique_attributes]: This job can take the objects in a register and updates them within a database table.  Attributes defines which object properties to convert to SQL SET clauses while unique_attributes translate to WHERE clauses.  Refer to the class and constructor specification for more detail.
 
 ### Dbee Jobs
@@ -194,11 +194,12 @@ There should now be two new patients, AB0 and AB1, present in the table `patient
 Notes:
 
 * Since we specified the `primary_key`, the records' `id` attributes should be set to their respective primary key values.
+* Composite primary keys are not currently supported.
 * Set `debug: true` to print out each INSERT statement in the output (not for production use.)
 
 #### Inserting Only New Records
 
-Another job `db_fuel/active_record/find_or_insert` allows for an existence check to performed each insertion.  If a record is found then it will not insert the record.  If `primary_key` is set then the existence check will also still set the primary key on the payload's respective object. We can build on the above insert example for only inserting new patients if their chart_number is unique:
+Another job `db_fuel/active_record/find_or_insert` allows for an existence check to performed each insertion.  If a record is found then it will not insert the record.  If `primary_key` is set then the existence check will also still set the primary key on the payload's respective object.  Note that composite primary keys are not currently supported. We can build on the above insert example for only inserting new patients if their chart_number is unique:
 
 ````ruby
 pipeline = {

data/lib/db_fuel/library/active_record/find_or_insert.rb

@@ -29,7 +29,7 @@ module DbFuel
         #
         #   attributes:  Used to specify which object properties to put into the
         #                SQL statement and also allows for one last custom transformation
-        #                pipeline, in case the data calls for sql-specific transformers
+        #                pipeline, in case the data calls for SQL-specific transformers
         #                before insertion.
         #
         #   debug: If debug is set to true (defaults to false) then the SQL statements and

data/lib/db_fuel/library/active_record/insert.rb

@@ -26,7 +26,7 @@ module DbFuel
         #
         #   attributes:  Used to specify which object properties to put into the
         #                SQL statement and also allows for one last custom transformation
-        #                pipeline, in case the data calls for sql-specific transformers
+        #                pipeline, in case the data calls for SQL-specific transformers
         #                before insertion.
         #
         #   debug: If debug is set to true (defaults to false) then the SQL statements and

data/lib/db_fuel/library/active_record/update.rb

@@ -28,7 +28,7 @@ module DbFuel
         #
         #   attributes:  Used to specify which object properties to put into the
         #                SQL statement and also allows for one last custom transformation
-        #                pipeline, in case the data calls for sql-specific transformers
+        #                pipeline, in case the data calls for SQL-specific transformers
         #                before mutation.
         #
         #   debug: If debug is set to true (defaults to false) then the SQL statements and

data/lib/db_fuel/modeling/keyed_column.rb

@@ -9,9 +9,9 @@
 
 module DbFuel
   module Modeling
-    # Connects a hash key to a sql column.  By default if a column is not given then its
+    # Connects a hash key to a SQL column.  By default if a column is not given then its
     # key will be used for both.  The general use case for this is for mapping objects
-    # to sql and sql to objects.
+    # to SQL and SQL to objects.
     class KeyedColumn
       acts_as_hashable
 

data/lib/db_fuel/version.rb

@@ -8,5 +8,5 @@
 #
 
 module DbFuel
-  VERSION = '1.1.0-alpha.1'
+  VERSION = '1.1.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: db_fuel
 version: !ruby/object:Gem::Version
-  version: 1.1.0.pre.alpha.1
+  version: 1.1.0
 platform: ruby
 authors:
 - Matthew Ruggio
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-11-28 00:00:00.000000000 Z
+date: 2020-12-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -268,9 +268,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '2.5'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubygems_version: 3.0.3
 signing_key: