lograge-sql 1.0.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 343ebf78f41cbfd1e384396332b6de047e2bfeba1dcf15e506031eb1011d61b5
-  data.tar.gz: 9fa97f78afc6f171873dc9df135ed7a91de505f522fff56894e8903c0159a37f
+  metadata.gz: 11cea1c366c76e19619e78e5d957f863cefa1fd5ec55a2330242cde0a92adc42
+  data.tar.gz: 343afe00dbf0ef4755400c9c234c12cf60806572a723f825c75e36a9e78ecbb2
 SHA512:
-  metadata.gz: 2a631a9bc6e7e209d23e9b05378e188fe00c29a449749d97ea372d8575b5ba868377ffa9151cd68f9ff6e063e0642abe8787b5076dada7e4991563a5578f65c5
-  data.tar.gz: 3b8ba8654bdab6404862c8961d6f68c09af5c78ee7e3409e3f225e011c9e423dd312193459df7e55997e542892d56a3b5bd272b26797f071b08bf693f6f142fb
+  metadata.gz: af84fccad7b7f4f98e44b4dfbf7fe95c73adefd0e09c552d6a5b3857564b674b8d0a177d28c37f9a03d34348a467cd9ddbadd343f4954fd91f68a2870ba7d079
+  data.tar.gz: 47b359c21d2549d575b4f8eb672927da8ac1baaa4a719e738d7ce735a72503bc41da6260502fec8b8e540d75380af78f7c23cbc570ecfc8239882255675ea4d9

data/README.md

@@ -33,7 +33,7 @@ Object Load (0.42) SELECT "objects.*" FROM "objects"
 Associations Load (0.42) SELECT "associations.*" FROM "associations" WHERE "associations"."object_id" = "$1"
 ```
 
-However, having `Lograge::Formatters::Json.new`, the relevant output is 
+However, having `Lograge::Formatters::Json.new`, the relevant output is
 
 ```json
 {
@@ -60,6 +60,9 @@ Rails.application.configure do
 end
 ```
 
+#### Thread-safety
+
+[Depending on the web server in your project](https://github.com/steveklabnik/request_store#the-problem) you might benefit from improved thread-safety by adding [`request_store`](https://github.com/steveklabnik/request_store) to your Gemfile. It will be automatically picked up by `lograge-sql`.
 
 ## Contributing
 

data/lib/lograge/sql.rb

@@ -17,6 +17,10 @@ module Lograge
         Lograge::Sql.extract_event = config.extract_event || default_extract_event
       end
 
+      def store
+        defined?(RequestStore) ? RequestStore.store : Thread.current
+      end
+
       private
 
       # By default, the output is a concatenated string of all extracted events

data/lib/lograge/sql/extension.rb

@@ -11,10 +11,10 @@ module Lograge
 
       # Collects all SQL queries stored in the Thread during request processing
       def extract_sql_queries
-        sql_queries = Thread.current[:lograge_sql_queries]
+        sql_queries = Lograge::Sql.store[:lograge_sql_queries]
         return {} unless sql_queries
 
-        Thread.current[:lograge_sql_queries] = nil
+        Lograge::Sql.store[:lograge_sql_queries] = nil
         {
           sql_queries: Lograge::Sql.formatter.call(sql_queries),
           sql_queries_count: sql_queries.length
@@ -33,8 +33,8 @@ module Lograge
       ActiveRecord::LogSubscriber.runtime += event.duration
       return if event.payload[:name] == 'SCHEMA'
 
-      Thread.current[:lograge_sql_queries] ||= []
-      Thread.current[:lograge_sql_queries] << Lograge::Sql.extract_event.call(event)
+      Lograge::Sql.store[:lograge_sql_queries] ||= []
+      Lograge::Sql.store[:lograge_sql_queries] << Lograge::Sql.extract_event.call(event)
     end
   end
 end

data/lib/lograge/sql/version.rb

@@ -3,6 +3,6 @@
 module Lograge
   module Sql
     # Gem version
-    VERSION = '1.0.0'
+    VERSION = '1.1.0'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: lograge-sql
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors:
 - Mattia Giuffrida
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-09-13 00:00:00.000000000 Z
+date: 2019-09-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord