dynamic-records-meritfront 3.0.24 → 3.0.26

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7452d0058119526d1ece08203106f8ae07da51f41e22f764c4d5262d2340e7f4
-  data.tar.gz: 88fc11727ba9a6d016afb22ec03beafc30412e37502daf35e33dce6532ef02b1
+  metadata.gz: e61d44017d347ec7083448f67c2a3db1994f49b2a63c21d27c976c8a06c6b777
+  data.tar.gz: bbc308253515c6db53e9964701745fbbee832aee9acd7d4c1d64812b532955f3
 SHA512:
-  metadata.gz: 69eff49f3efbfd1261477cd3b895786a0dc97ca09e2933aab4471eea85c61f4e54651d37a4d3138e4c9d7c64f4802c3fda0d45152d84598e206072a14b828089
-  data.tar.gz: e6a26b39284b4b80891fed68af41d930b1d12e83aaadad45c8d6fee4c9f1bfadbaebd3ff56407a09b5714f2248d3cf39cdb58a37cc4a8835241933294f99a2d9
+  metadata.gz: f5a7ae8e89825cf74e31e99e4e422087f3eacc9bb290c727c49ec272c8a40f507d932d3e64f85ee43edf8366c6b2fe6121f3303204ff759e838aaa435ea46c55
+  data.tar.gz: d70bb9d0a4ab3972ad2f940f0606a1cad2b492ad5fc8daafa892d6014800513ae4d54d2d1d3d1f47d62c3b3bcd5f89c9100173e773cb042dceef4d0b5af4fbd4

data/Gemfile.lock

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

data/README.md

@@ -315,6 +315,52 @@ the output:
    ...]}
 ```
 </details>
+
+<details>
+<summary>above example with relations (no need for dynamic_attach)</summary>
+#get list of users, those users friends, and who those users follow, all in one request.
+
+```ruby
+    friend_attach = attach_on: Proc.new {|users_friend|
+        users_friend.friended_to
+    }
+   
+   output = ApplicationRecord.instaload_sql([
+      User.instaload(%Q{
+              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
+         from friends
+	     inner join limited_users on limited_users.id = bigger_user_id
+         union
+         select friends.bigger_user_id as id, friends.smaller_user_id as friended_to
+	 from friends
+	     inner join limited_users ON limited_users.id = smaller_user_id
+      }, table_name: :users_friends, base_name: :limited_users, attach_on: attach_on),
+      ApplicationRecord.instaload(%Q{
+         SELECT follows.followable_id, follows.follower_id
+         FROM follows
+         INNER JOIN limited_users ON follows.follower_id = limited_users.id
+      }, table_name: :users_follows, base_name: :limited_users)
+   ], user_ids: uids, time: t)
+   
+   pp out['limited_users']
+
+```
+sql output: same as example above this example
+
+printed output (same as in dynamic attach example): 
+```ruby
+#<User id: 3, users_friends: [#<User id: 5, friended_to: 3>, #<User id: 6, friended_to: 3>, #<User id: 21, friended_to: 3>], users_follows: [{"followable_id"=>935, "follower_id"=>3}, {"followable_id"=>938, "follower_id"=>3}, ...]>,
+ #<User id: 14, users_friends: [#<User id: 9, friended_to: 14>, #<User id: 21, friended_to: 14>, ...], users_follows: [{"followable_id"=>936, "follower_id"=>14}, {"followable_id"=>937, "follower_id"=>14}, {"followable_id"=>938, "follower_id"=>14}, ...]>,
+ #<User id: 9, users_friends: [#<User id: 14, friended_to: 9>, #<User id: 22, friended_to: 9>, ...], users_follows: [{"followable_id"=>938, "follower_id"=>9}, {"followable_id"=>937, "follower_id"=>9}, ...]>,
+ #<User id: 19, users_friends: [#<User id: 1, friended_to: 19>, #<User id: 18, friended_to: 19>, ...], users_follows: [{"followable_id"=>935, "follower_id"=>19}, {"followable_id"=>936, "follower_id"=>19}, {"followable_id"=>938, "follower_id"=>19}, ...]>,
+ ```
+	
+</details>
 	
 #### self.instaload(sql, table_name: nil, relied_on: false, dont_return: false)
 A method used to prepare data for the instaload_sql method. It returns a hash of options.
@@ -470,6 +516,9 @@ v3.0.6
 - changed how variables are set for ActiveRecord objects, I gave up on figuring out what ActiveRecord is doing for *the most part* and i now just do a eval("self.#{parameter}=value") type deal. Works well. Allows you to override relations when doing polymorphic stuff which is a pretty big use case.
 - I am thinking of changing how arrays are handled as that is really the only postgresql based dependency here and that will allow the library to open up to other databases. Issue is all the code I have already written in my app dependant on such things.
 
+3.0.24
+- changed how questionable_attribute_set works again, this time by using attr_accessors on the singleton class. Seems to paper over the default reflections nicely which has been a huge issue. They use this weird delegate thing which has been throwing me off. Anyway, no more evals which is nice. This fixed an issue with dynamic attach one-to-many relations.
+
 ## Questions
 - Q: does the name of a sql operation have anything to do with prepared statements?
 - A: no, the prepared statement determines uniqueness in some other way, dont worry about collisions. The only issue with prepared statements that I can determine is when you write a statement where things change every time, thus preparing potentially infinite prepared statements. This can be alleviated by using sql arguments correctly. Using arguments correctly also will stop sql injection attacks so. You know. Do it properly. Dont just hard code them into the query.

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

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

data/lib/dynamic-records-meritfront.rb

@@ -1,7 +1,7 @@
 require "dynamic-records-meritfront/version"
 require 'hashid/rails'
 
-#this file contains multiple classes which should honestly be split up
+#this file contains multiple classes which should honestly be split up.
 
 module DynamicRecordsMeritfront
     extend ActiveSupport::Concern
@@ -87,12 +87,10 @@ module DynamicRecordsMeritfront
             Time => ActiveModel::Type::Time,
             Float => ActiveModel::Type::Float,
 		NilClass => ActiveModel::Type::Boolean,
-            Array =>  Proc.new{ |first_el_class| ActiveRecord::ConnectionAdapters::PostgreSQL::OID::Array.new(DB_TYPE_MAPS[first_el_class].new) }
+            Array =>  Proc.new{ |first_el_class| ActiveRecord::ConnectionAdapters::PostgreSQL::OID::Array.new(DB_TYPE_MAPS[first_el_class].new) } #this one was a mistake
         }
 
         def convert_to_query_attribute(name, v)
-            #yes its dumb I know dont look at me look at rails
-
             # https://stackoverflow.com/questions/40407700/rails-exec-query-bindings-ignored
             # binds = [ ActiveRecord::Relation::QueryAttribute.new(
             # 	"id", 6, ActiveRecord::Type::Integer.new
@@ -294,8 +292,8 @@ module DynamicRecordsMeritfront
 
         self.dynamic_reflections ||= []
         dyna = dynamic_reflections.map{|dr|
-            self.method(dr.to_sym).call()
-        }
+            [dr, self.method(dr.to_sym).call()]
+        }.to_h
 
         if dyna.any?
             "#<#{self.class} #{inspection} | #{dyna.to_s}>"
@@ -954,8 +952,9 @@ module DynamicRecordsMeritfront
 
     #just for ease of use
     def headache_preload(records, associations)
-            self.class.headache_preload(records, associations)
+        self.class.headache_preload(records, associations)
     end
+
     def safe_increment(col, val) #also used in follow, also used in comment#kill
         self.class.where(id: self.id).update_all("#{col} = #{col} + #{val}")
     end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dynamic-records-meritfront
 version: !ruby/object:Gem::Version
-  version: 3.0.24
+  version: 3.0.26
 platform: ruby
 authors:
 - Luke Clancy