dynamic-records-meritfront 3.1.0 → 3.1.29

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 187dd89025805fae04c8f188a900f6373cfd84584a720787dec852c0281a2060
-  data.tar.gz: 778e0e23ede44cc3fbb304e7216d4846745c25cb0e9fc1d87c8871375b21efcb
+  metadata.gz: 0e329f6fa51f14843549a6d3681870a99a5e1b9ff78af32281ca8a5433122922
+  data.tar.gz: 5c14dc25ee35ea526f220d5b727032dcaf1be0f1bb744c080c9a12c4a70b15bb
 SHA512:
-  metadata.gz: e1071cf066822a8da8b1bf522c51c80e012b7e8c8c137aa3c7666a2965952d254bd863d4fbb9df4d77192458ff0b744a96e01e7485f2be6a94fc1faa37b1fe7f
-  data.tar.gz: eebfbac3a6a3c0202255f15bad0ced512d8c60c79f601aaada4706790a5af518c06b7413dce5ffb38e6f5e9e8318de7221ae12049ec4129f1ed23a7efb55b1d4
+  metadata.gz: 19070cbac3c6442ba5ba82c28d370efe9a3cc6cfd0e6a05e5a74175982000484baa804baceb187b00badb865ba57e6f9059bf878670c518830c97ea904157779
+  data.tar.gz: 85892bfa3f8708bbb683297513ffb0f10650ad389084a219203241918e52208041c29a477e478027e3f841e0235b983fd1948f1ff65389b34efcbe18c531b805

data/Gemfile.lock

@@ -1,31 +1,45 @@
 PATH
   remote: .
   specs:
-    dynamic-records-meritfront (3.1.0)
+    dynamic-records-meritfront (3.1.29)
       hashid-rails
 
 GEM
   remote: https://rubygems.org/
   specs:
-    activemodel (7.0.4.2)
-      activesupport (= 7.0.4.2)
-    activerecord (7.0.4.2)
-      activemodel (= 7.0.4.2)
-      activesupport (= 7.0.4.2)
-    activesupport (7.0.4.2)
+    activemodel (7.1.1)
+      activesupport (= 7.1.1)
+    activerecord (7.1.1)
+      activemodel (= 7.1.1)
+      activesupport (= 7.1.1)
+      timeout (>= 0.4.0)
+    activesupport (7.1.1)
+      base64
+      bigdecimal
       concurrent-ruby (~> 1.0, >= 1.0.2)
+      connection_pool (>= 2.2.5)
+      drb
       i18n (>= 1.6, < 2)
       minitest (>= 5.1)
+      mutex_m
       tzinfo (~> 2.0)
-    concurrent-ruby (1.2.0)
+    base64 (0.1.1)
+    bigdecimal (3.1.4)
+    concurrent-ruby (1.2.2)
+    connection_pool (2.4.1)
+    drb (2.1.1)
+      ruby2_keywords
     hashid-rails (1.4.1)
       activerecord (>= 4.0)
       hashids (~> 1.0)
     hashids (1.0.6)
-    i18n (1.12.0)
+    i18n (1.14.1)
       concurrent-ruby (~> 1.0)
-    minitest (5.17.0)
+    minitest (5.20.0)
+    mutex_m (0.1.2)
     rake (12.3.3)
+    ruby2_keywords (0.0.5)
+    timeout (0.4.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
 

data/README.md

@@ -5,8 +5,7 @@ Dyanmic Records Meritfront helps extend active record functionality to make it m
 2. communicate with the backend more effectively with sql queries. This becomes especially relevant when you hit the limits of Active Record Relations and the usual way of querying in rails. For instance, if you have dynamic sql queries that are hard to convert properly into ruby.
 3. add other helper methods to work with your database, such as checking if relations exist, or if a migration has been run.
 
-Note that postgres is currently a requirement for using arrays in this gem. If it becomes an issue send me a pull request or an issue or somethin.
-Also note that the gem has not been tested outside of postgres.
+Note that you will have issues using the gem outside of postgres. These issue can be fixed, and I am considering a major version update to fix them. Let me know and I will probably do it.
 
 ## Basic Examples
 ```ruby
@@ -55,7 +54,7 @@ class ApplicationRecord < ActiveRecord::Base
 end
 ```
 
-### SQL methods
+## SQL methods
 
 Methods written for easier sql usage.
 
@@ -368,6 +367,10 @@ A method used to prepare data for the instaload_sql method. It returns a hash of
 - 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)
 - dont_return: when used with relied_on makes it so that this data is not returned to rails from the database.
+- base_on: for relations, a proc describing how to attach to the base table
+- base_name: for relations, the table name for the table to attach to
+- attach_on: for relations, a proc describing how this table attaches to the the base table
+- one_to_one: for relations, a boolean that flips one-to-many/one-to-one (default false)
 
 note that the order of the instaload methods matter depending on how they reference eachother.
 <details>
@@ -393,7 +396,7 @@ taking the output of the instaload_sql method, this method creates relations bet
 - 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}
-- attach_on: put a proc here to override the matching key for the attach table. Default is, for a user and post type, {|post| post.user_id}
+- attach_on: put a proc here to override the matching key for the attach table. Default is, for a user and post type, {|post| post.user_id}. Returning an array from this proc will make this object attach to base records that have one of those keys. This can be used with GROUP BY and ARRAY_AGG functions to stop duplicate rows while still attaching where needed. Think of attaching a user to a post where multiple posts can have the same user.
 - one_to_one: switches between a one-to-one relationship or not
 
 <details> 
@@ -421,7 +424,7 @@ printed output:
 
 </details>
 	
-### Hashed Global IDS
+## Hashed Global IDS
 
 hashed global ids look like this: "gid://meritfront/User/K9YI4K". They also have an optional tag so it can also look like "gid://meritfront/User/K9YI4K@user_image". They are based on global ids.
 
@@ -448,7 +451,9 @@ See the hashid-rails gem for more (https://github.com/jcypret/hashid-rails). Als
 
 ## Potential Issues
 
-- This gem was made with a postgresql database. This could cause a lot of issues with the sql-related methods if you do not. I dont have the bandwidth to help switch it elsewhere, but if you want to take charge of that, I would be more than happy to assist by answering questions an pointing out any areas that need transitioning.
+- This gem was made with a postgresql database. There will be some issues when using other databases. Let me know and I will help you out how I can. The main issue as far as i can tell in the transition will be with
+	1. dynamic_sql arrays. I assumed going into this that prepared statements were generated when the sql or name of the sql changed *at all*. This is not true, prepared statements are generated based on the underlying logical flow of the request. Because of this I was treating List types as postgresql array data types. Instead I should of converted them to ($1,$2,$3,$4,...etc) strings. This change would make them act similarly to how Lists of Lists are treated currently. This change would make necessary a major version change. There would also need to be an option to roll back to postgresql arrays on a case by case basis for backwards compatibility.
+	2. instaload_sql. The instaload_sql request has hardcoded sql in it that has not been tested on other databases. This may be especially problematic due to the use of the json data-type.
 - If you return a password column (for example) as pwd, this gem will accept that. That would mean that the password could me accessed as model.pwd. This is cool - until all passwords are getting logged in production servers. So be wary of accessing, storing, and logging of sensative information. Active Record has in built solutions for this type of data, as long as you dont change the column name. This gem is a sharp knife, its very versitile, but its also, you know, sharp.
 	
 ## Changelog
@@ -496,7 +501,7 @@ since things may be broken already, it seemed like a good time to do this.
   - this also tells me that uniq'ing variables to decrease the number of them was a bad idea which could cause random failures.
 - functionality improvements
   - The biggest change is that names are now optional! name_modifiers is now depreciated functionality as it serves no useful purpose. Will leave in for compatibility but take out of documentation. Used to think the name was related to prepared statements. This will lead simpler ruby code.
-  - If name is left out, the name will be set to the location in your app which called the method. For example, when dynamic_sql was called from irb, the name was: "(irb):45:in `irb_binding'". This is done using stack trace functionality. In another case the name was "app/models/report.rb:364:in `refresh_db_methods'"
+  - If name is left out, the name will be set to the location in your app which called the method. For example, when dynamic_sql was called from irb, the name was: "(irb):45:in 'irb_binding'". This is done using stack trace functionality. In another case the name was "app/models/report.rb:364:in 'refresh_db_methods'"
   - dynamic_instaload_sql is now just instaload_sql. dynamic_instaload_sql has been aliased.
   - Name is optional on instaload_sql aswell
   - MultiAttributeArrays (array's of arrays) which can be passed into dynamic_sql largely for inserts/upserts will now treat symbols as an attribute name. This leads to more consise sql without running into above error.
@@ -517,7 +522,22 @@ v3.0.6
 - 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.
+- 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 relation 
+
+3.1.0
+- will try keeping breaking changes out of minor version here-on-out.
+- better debugging messages and warnings for instaload
+- returning an array in the attach_on proc will now treat each item in the array as its own attach_on key instead of all as one key. So for example you can attach one user to multiple posts, and only return one user object from the database.
+- see the dynamic_attach docs above for more on that attach_on thing.
+....
+- took out undocumented quick_safe_increment and safe_increment as they were not relevant to the gem - and fairly basic.
+
+3.1.28
+- warning messages for dynamic_attach. to_s'd any provided table_names for ease-of-use.
+- logging info for dynamic_attach outside of instaload.
+- fixed an error where instaload only worked with ApplicationRecord abstract_class. Now works on anything thats a subclass of ActiveRecord::Base
+- wow
+
 
 ## Questions
 - Q: does the name of a sql operation have anything to do with prepared statements?
@@ -525,7 +545,7 @@ v3.0.6
 - Q: The default name of my sql statements looks like a stack trace? Whats going on?
 - A: We set the location of where you called the function as the default name for easy debugging. Its not an error, we just take some info from the stacktrace. It also includes the method name which can provide some insite into what the query is doing. Makes logs alot nicer to look at.
 - Q: Whats MeritFront?
-- A: I am making a social media platform
+- A: I am making a social media platform. See meritfront.com, Its soft launched.
 - Q: Inspect on user records doesn't seem to work properly
 - A: inspect is overwritten by many diffrent libraries, in terms of devise for example, they override our override of active record's inspect. The best way to deal with this is to look at the source location of these methods and bring them together (user.method(:inspect).source_location). In my case with devise, i ended up with this in the user record:
 ```ruby

data/bin/update

@@ -51,5 +51,8 @@ puts `git commit -m 'minor changes to version #{version_new}'`
 puts "_______________________________________________"
 puts "INSTALL GEM LOCALLY"
 puts `bundle exec rake install`
+puts "note if you cant install in your project u prob have different ruby versions for the project and this folder."
+puts "if in that case and using rbenv, change your global ruby version under ~/.rbenv/version or your local by adding"
+puts "somthing similar in a .ruby_version file. Not using .rbenv? Add ur instructions here"
 puts "_______________________________________________"
 puts "info: write 'bundle exec rake release' to release the current version to the interwebz"

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

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

data/lib/dynamic-records-meritfront.rb

@@ -78,6 +78,7 @@ module DynamicRecordsMeritfront
         DB_TYPE_MAPS = {
             String => ActiveModel::Type::String,
             Symbol => ActiveModel::Type::String,
+            ActiveSupport::SafeBuffer => ActiveModel::Type::String,
             Integer => ActiveModel::Type::BigInteger,
             BigDecimal => ActiveRecord::Type::Decimal,
             TrueClass => ActiveModel::Type::Boolean,
@@ -104,7 +105,7 @@ module DynamicRecordsMeritfront
 
             type = DB_TYPE_MAPS[v.class]
             if type.nil?
-                raise StandardError.new("#{name} (of value: #{v}, class: #{v.class}) unsupported class for ApplicationRecord#headache_sql")
+                raise StandardError.new("#{name} (of value: #{v}, class: #{v.class}) unsupported class for DynamicRecordsMeritfront#headache_sql")
             elsif type.class == Proc
                 a = v[0]
                 # if a.nil?
@@ -399,9 +400,14 @@ module DynamicRecordsMeritfront
                 if returns_nil
                     return nil
                 else
-                    raise StandardError.new("non-string class passed to ApplicationRecord#locate_hgid as the hgid_string variable")
+                    raise StandardError.new("non-string class passed to DynamicRecordsMeritfront#locate_hgid as the hgid_string variable")
                 end
             end
+            if PROJECT_NAME == 'midflip'
+                #should be fine to take out in a month or so, just got lazy and pretty sure I am the only one using this gem.
+                #dont want to kill me jobs.
+                hgid_string = hgid_string.gsub('ApplicationRecord', 'Record')
+            end
             if hgid_string.include?('@')
                 hgid_string = hgid_string.split('@')
                 hgid_string.pop
@@ -437,7 +443,7 @@ module DynamicRecordsMeritfront
                 nil
             else
                 #stops execution as default
-                raise StandardError.new 'Not the expected class, or a subclass of ApplicationRecord if called on that.'
+                raise StandardError.new 'Not the expected class or subclass.'
             end
         end
         def get_hgid_tag(hgid_string)
@@ -653,37 +659,31 @@ module DynamicRecordsMeritfront
             insta_array = insta_array.select{|ar| not ar[:dont_return]}
             ret_hash = insta_array.map{|ar| [ar[:table_name].to_s, []]}.to_h
             opts[:raw] = true
-            ApplicationRecord.headache_sql(name, sql, opts).rows.each{|row|
+
+            #annoying bug
+            s = self
+            unless s.abstract_class?
+                s = s.superclass
+            end
+            
+            s.dynamic_sql(name, sql, opts).rows.each{|row|
                 #need to pre-parsed as it has a non-normal output.
                 table_name = row[2]
                 klass = row[1].constantize
                 json = row[0]
                 parsed = JSON.parse(json)
-
                 ret_hash[table_name].push dynamic_init(klass, parsed)
             }
 
-            insta_array = insta_array.map{|a|a.delete(:sql); next a} #better for debuggin and we dont need it anymore
+            insta_array.each{|a| a.delete(:sql)}
             
             #formatting options
             for insta in insta_array
                 if insta[:base_name]
                     #in this case, 'as' is meant as to what pseudonym to dynamicly attach it as
-                    n_attached = dynamic_attach(ret_hash, insta[:base_name], insta[:table_name], base_on: insta[:base_on], attach_on: insta[:attach_on],
+                    #we are attaching to the base table. Variable could of been less confusing. My bad.
+                    dynamic_attach(ret_hash, insta[:base_name], insta[:table_name], base_on: insta[:base_on], attach_on: insta[:attach_on],
                         one_to_one: insta[:one_to_one], as: insta[:as])
-
-                    if Rails.logger.level <= 1
-                        tn = insta[:table_name]
-                        bn = insta[:base_name]
-                        tc = ret_hash[tn].count
-                        btc = ret_hash[bn].count
-
-                        if insta[:as]
-                            Rails.logger.debug "#{n_attached} attached from #{tn}(#{tc}) as #{insta[:as]} -> #{bn}(#{btc})"
-                        else
-                            Rails.logger.debug "#{n_attached} attached from #{tn}(#{tc}) -> #{bn}(#{btc})"
-                        end
-                    end
                 elsif insta[:as]
                     Rails.logger.debug "#{insta[:table_name]} as #{insta[:as]}"
                     #in this case, the idea is more polymorphic in nature. unless they are confused and just want to rename the table (this can be done with
@@ -707,7 +707,7 @@ module DynamicRecordsMeritfront
             m = model_with_an_id_column_and_timestamps
             ar = m.superclass
             mtname = m.table_name
-            ApplicationRecord.transaction do
+            transaction do
                 puts 'test recieving columns not normally in the record.'
                 rec = m.dynamic_sql(%Q{
                     SELECT id, 5 AS random_column from #{mtname} LIMIT 10
@@ -799,12 +799,23 @@ module DynamicRecordsMeritfront
         def dynamic_attach(instaload_sql_output, base_name, attach_name, base_on: nil, attach_on: nil, one_to_one: false, as: nil)
             #as just lets it attach us anywhere on the base class, and not just as the attach_name.
             #Can be useful in polymorphic situations, otherwise may lead to confusion.
+            
+            #oh the errors
+            base_name = base_name.to_s
+            attach_name = attach_name.to_s
+
             as ||= attach_name
 
             base_arr = instaload_sql_output[base_name]
             
             #return if there is nothing for us to attach to.
-            return 0 if base_arr.nil? or not base_arr.any?
+            if base_arr.nil?
+                Rails.logger.error("base table " + base_name + " was not set")
+                return 0
+            elsif not base_arr.any?
+                Rails.logger.debug("no items in base table " + base_name)
+                return 0
+            end
 
             #set variables for neatness and so we dont compute each time
             #	base class information
@@ -829,7 +840,14 @@ module DynamicRecordsMeritfront
 
             #make sure the attach class has something going on. We do this after the default stage
             attach_arr = instaload_sql_output[attach_name]
-            return 0 if attach_arr.nil? or not attach_arr.any?
+            
+            if attach_arr.nil?
+                Rails.logger.error("attaching table " + attach_name + " was not set")
+                return 0
+            elsif not attach_arr.any?
+                Rails.logger.debug("no items in attach table " + attach_name)
+                return 0
+            end
             
             #   attach class information
             attach_class = attach_arr.first.class
@@ -922,7 +940,7 @@ module DynamicRecordsMeritfront
                         if base_rec
                             dupl = duplicates_base.include? ak
                             if dupl
-                                Rails.logger.warn "WARNING in #{attach_name} -> #{base_name}. Duplicate base_on key being utilized (this is usually in error). Only one base record will have an attachment. For the base table, consider using GROUP BY for your id and ARRAY_AGG for the base_on column."
+                                Rails.logger.warn "WARNING in #{attach_name} -> #{base_name}. Duplicate base_on key being utilized (this is usually in error). Only one base record will have an attachment. For the base table, consider using GROUP BY id and ARRAY_AGG for the base_on column."
                                 Rails.logger.warn "base_on key: #{ak.to_s}"
                             end
                             
@@ -933,6 +951,14 @@ module DynamicRecordsMeritfront
                 end
             }
 
+            if Rails.logger.level <= 1
+                if as
+                    Rails.logger.debug "#{x}/#{attach_arr.count} attached from #{attach_name} as #{as} -> #{base_name}(#{x}/#{base_arr.count})"
+                else
+                    Rails.logger.debug "#{x}/#{attach_arr.count} attached from #{attach_name} -> #{base_name}(#{x}/#{base_arr.count})"
+                end
+            end
+
             return x
         end
         alias swiss_attach dynamic_attach
@@ -955,10 +981,11 @@ module DynamicRecordsMeritfront
                 return record
             end
         end
-
-        def quick_safe_increment(id, col, val)
-            where(id: id).update_all("#{col} = #{col} + #{val}")
-        end
+		
+		#undocumented and simple
+        #def quick_safe_increment(id, col, val)
+         #   where(id: id).update_all("#{col} = #{col} + #{val}")
+        #end
 
         
     end
@@ -995,8 +1022,10 @@ module DynamicRecordsMeritfront
         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
+
+	#undocumented and simple
+ #   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
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dynamic-records-meritfront
 version: !ruby/object:Gem::Version
-  version: 3.1.0
+  version: 3.1.29
 platform: ruby
 authors:
 - Luke Clancy
-autorequire:
+autorequire: 
 bindir: exe
 cert_chain: []
-date: 2023-02-13 00:00:00.000000000 Z
+date: 2023-10-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: hashid-rails
@@ -54,7 +54,7 @@ metadata:
   homepage_uri: https://github.com/LukeClancy/dynamic-records-meritfront
   source_code_uri: https://github.com/LukeClancy/dynamic-records-meritfront
   changelog_uri: https://github.com/LukeClancy/dynamic-records-meritfront/blob/main/README.md
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -69,8 +69,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.7
-signing_key:
+rubygems_version: 3.4.10
+signing_key: 
 specification_version: 4
 summary: Helpers for active record that allow for more abstract and fine-grained code.
 test_files: []