dynamic-records-meritfront 3.0.3 → 3.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 15173d17ad833e673910fc87f1dd1c6801105086f9a36e2042154c3e624fbc50
-  data.tar.gz: 171e89a86eef3b0f75a92a75b4226ab401eda42ad9dd83bb4bed16b92ae439db
+  metadata.gz: aa816c1fc2d4e08950ff1f91c1bb4aa1d8025a4e845d62919e7254e449a6901f
+  data.tar.gz: 4649ad599b97346ca16ddbb5f07298fd0408d5028795fcfcb3e5f0b5d1f906c9
 SHA512:
-  metadata.gz: 20cae9b9c791929d29002d171a837291c1e9315dc9bbb6b4a408212dd98ce408aae270a1b52caeb91f73995ac086e4ff9afd771b9a2a51878bea400881141c88
-  data.tar.gz: 551ef2074974ae385c9759ac58c2c170faeb835ed87ca166d7ccfe38779b6f2d03d2f3a3fc06c53e3a05c38a93ccf014a240f13a7b78eb227810d8fcc5928151
+  metadata.gz: 2dbba9dee9ca11dab5665b0d96a2b13840f7bfff8eb28c859e8628119efb420924435ed06ca380dc9fec7408231cf7a7f9671429cc34c18c2e0536646324a3ba
+  data.tar.gz: cddf05b9c1f9eb9df8c1c7fb1a586dc618eed8a5f3fd0a0b8f8b4017d3bbb0beee66143c4925bd102af52d2ea6e302c5fda7384ca8c4f7cfafa8b481afefc0f8

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    dynamic-records-meritfront (3.0.3)
+    dynamic-records-meritfront (3.0.6)
       hashid-rails
 
 GEM

data/README.md

@@ -67,7 +67,7 @@ A better and safer way to write sql. Can return either a Hash, ActiveRecord::Res
 
 ```ruby
 User.dynamic_sql('select * from users')	#returns all users
-ApplicationRecord.dynamic_sql('select id from users', raw: true).rows.flatten #get just the users ids
+ApplicationRecord.dynamic_sql('select * from users') #returns all user column information in an array
 ```
 
 with options: 
@@ -149,27 +149,28 @@ Get users who match a list of ids. Uses a postgresql Array, see the potential is
 Do an upsert
 
 ```ruby
+	time = DateTime.now
 	rows = uzrs.map{|u| [
 		u.id,		#user_id
 		self.id,	#conversation_id
 		from,		#invited_by
-		t,		#created_at
-		t,		#updated_at
+		:time,		#created_at		(We use symbols to denote other sql arguments)
+		:time,		#updated_at
 	]}
 	ApplicationRecord.dynamic_sql("upsert_conversation_invites_2", %Q{
 		INSERT INTO conversation_participants (user_id, conversation_id, invited_by, created_at, updated_at)
 		VALUES :rows
 		ON CONFLICT (conversation_id,user_id)
 		DO UPDATE SET updated_at = :time
-	}, rows: rows, time: t)
+	}, rows: rows, time: time)
 ```
-This will output sql similar to below. Note this can be done for multiple conversation_participants. Also note that it only sent one time variable as an argument as dynamic_sql detected that we were sending duplicate information.
+This will output sql similar to below. Note this can be done for multiple conversation_participants. Also note that we sent only one time variable during our request instead of duplicating it.
 ```sql
 	INSERT INTO conversation_participants (user_id, conversation_id, invited_by, created_at, updated_at)
 	VALUES ($1,$2,$3,$4,$4)
 	ON CONFLICT (conversation_id,user_id)
 	DO UPDATE SET updated_at = $4
-	-- [["rows_1", 15], ["rows_2", 67], ["rows_3", 6], ["rows_4", "2022-10-13 20:49:27.441372"]]
+	-- [["rows_1", 15], ["rows_2", 67], ["rows_3", 6], [:time, "2022-10-13 20:49:27.441372"]]
 ```
 </details>
 	
@@ -244,7 +245,7 @@ obj.has_association?(:votes) #false
 ```
 </details>
 
-#### self.dynamic_instaload_sql( *optional* name, insta_array, opts = { })
+#### self.instaload_sql( *optional* name, insta_array, opts = { })
 *instaloads* a bunch of diffrent models at the same time by casting them to json before returning them. Kinda cool. Maybe a bit overcomplicated. Seems to be more efficient to preloading when i tested it.
 - name is passed to dynamic_sql and is the name of the sql request
 - opts are passed to dynamic_sql (except for the raw option which is set to true. Raw output is not allowed on this request)
@@ -264,7 +265,7 @@ out = ApplicationRecord.instaload_sql([
 
 ```ruby
    # the ruby entered
-   output = ApplicationRecord.dynamic_instaload_sql([
+   output = ApplicationRecord.instaload_sql([
       User.instaload('SELECT id FROM users WHERE users.id = ANY (:user_ids) AND users.created_at > :time', table_name: 'limited_users', relied_on: true),
       User.instaload(%Q{
          SELECT friends.smaller_user_id AS id, friends.bigger_user_id AS friended_to
@@ -323,7 +324,7 @@ the output:
 </details>
 	
 #### self.instaload(sql, table_name: nil, relied_on: false, dont_return: false)
-A method used to prepare data for the dynamic_instaload_sql method. It returns a hash of options.
+A method used to prepare data for the instaload_sql method. It returns a hash of options.
 - klass called on: if called on an abstract class (ApplicationRecord) it will return a list of hashes with the data. Otherwise returns a list of the classes records.
 - table_name: sets the name of the temporary postgresql table. This can then be used in further instaload sql snippets.
 - relied_on: will make it so other instaload sql snippets can reference this table (it makes it use posrgresql's WITH operator)
@@ -349,7 +350,7 @@ User.instaload('SELECT id FROM users WHERE users.id = ANY (:user_ids) AND users.
 </details>
 
 #### self.dynamic_attach(instaload_sql_output, base_name, attach_name, base_on: nil, attach_on: nil, one_to_one: false)
-taking the output of the dynamic_instaload_sql, this method attaches the models together so they are attached.
+taking the output of the instaload_sql method, this method creates relations between the models.
 - base_name: the name of the table we will be attaching to
 - attach_name: the name of the table that will be attached
 - base_on: put a proc here to override the matching key for the base table. Default is, for a user and post type, {|user| user.id}
@@ -357,7 +358,7 @@ taking the output of the dynamic_instaload_sql, this method attaches the models
 - one_to_one: switches between a one-to-one relationship or not
 
 <details> 
-<summary> attach information for each limited_user in the dynamic_instaload_sql example </summary>
+<summary> attach information for each limited_user in the instaload_sql example </summary>
 	
 ```ruby
 	

data/lib/dynamic-records-meritfront/version.rb

@@ -1,5 +1,5 @@
 
 	module DynamicRecordsMeritfront
-	    VERSION = '3.0.3'
+	    VERSION = '3.0.6'
 	end
 	#this file gets overwritten automatically on minor updates, major ones need to be manually changed

data/lib/dynamic-records-meritfront.rb

@@ -17,7 +17,7 @@ module DynamicRecordsMeritfront
 		#should work, probably able to override by redefining in ApplicationRecord class.
 		#Note we defined here as it breaks early on as Rails.application returns nil
 		PROJECT_NAME = Rails.application.class.to_s.split("::").first.to_s.downcase
-        DYNAMIC_SQL_RAW = false
+        DYNAMIC_SQL_RAW = true
 	end
     class DynamicSqlVariables
         attr_accessor :sql_hash

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dynamic-records-meritfront
 version: !ruby/object:Gem::Version
-  version: 3.0.3
+  version: 3.0.6
 platform: ruby
 authors:
 - Luke Clancy
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2022-12-12 00:00:00.000000000 Z
+date: 2022-12-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: hashid-rails