pg_lock 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: d4751ff801966253cdbd7662bf288c44251b0c50
-  data.tar.gz: a826d5ee152d541b70dbd1a448cfabd005f6e100
+SHA256:
+  metadata.gz: e285d50b50c70bd26a8e9ce0047cb874450ebc27dc5db28c903ef613540ecaed
+  data.tar.gz: 8a167c46ae260ac9b84e0dd442f821a7d3a9894a4a72f206cb5fd669fcbf4594
 SHA512:
-  metadata.gz: 44720df9698d51ec531713d26faa8379df673b408b686892413af5122f32d8f1b7517561354bcacbc9ba0e323e4aa6b2a875cf49340f4d877b057757b14ee43e
-  data.tar.gz: 073c50e4bd05804b57cc22d019b4ca5def74c21032e52d9a31d9fcff20ca49da3fc72e0098c1292fdde2f20b6eef6638a91dd634c0accc9013015cc5e6484af7
+  metadata.gz: 23e058530b6b4029df92d8733ab7828753360c85092113a1dac14afab03ff8de6a1c926c8399a7f6833811b3963febd75bb1aeaefdfb8827ab3e44c13964e7e4
+  data.tar.gz: 7346e5463867c3a5755203c6c8e397e863d1d2756eeda5db4614dc525693d758270e02a9bb4b6ec8e686565410cec011f7be1657d480f5fcf1d35314bb0366a2

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # A Log of Changes!
 
+## [0.1.2] - 2017-12-06
+
+- Support Rails 5 and newer PG versions [#5]
+
 ## [0.1.1] - 2015-10-07
 
 - Allow setting default connection with constant.

data/README.md

@@ -182,6 +182,12 @@ Where `DB` is to be your database connection.
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `bin/console` for an interactive prompt that will allow you to experiment.
 
+To run tests you'll need a database:
+
+```
+$ createdb pg_lock_test
+```
+
 To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release` to create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
 
 ## Contributing

data/lib/pg_lock/locket.rb

@@ -1,6 +1,8 @@
 class PgLock
   # Holds the logic to aquire a lock and parse if locking was successful
   class Locket
+    TRUE_VALUES = [true, "t"].freeze
+
     attr_accessor :args, :connection
     def initialize(connection, lock_args)
       self.connection = connection
@@ -18,13 +20,13 @@ class PgLock
     end
 
     def aquired?
-      @lock[0]["pg_try_advisory_lock"] == "t"
+      TRUE_VALUES.include?(@lock[0]["pg_try_advisory_lock"])
     rescue
       false
     end
 
     def active?
-      connection.exec(<<-eos, args).getvalue(0,0) == "t"
+      active = connection.exec(<<-eos, args).getvalue(0,0)
         SELECT granted
         FROM pg_locks
         WHERE locktype = 'advisory' AND
@@ -33,6 +35,8 @@ class PgLock
          classid = $1 AND
          objid = $2
       eos
+
+      TRUE_VALUES.include?(active)
     end
   end
-end
+end

data/lib/pg_lock/version.rb

@@ -1,3 +1,3 @@
 class PgLock
-  VERSION = "0.1.1"
+  VERSION = "0.1.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pg_lock
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - mikehale
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2015-10-07 00:00:00.000000000 Z
+date: 2017-12-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: pg
@@ -124,7 +124,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5.1
+rubygems_version: 2.6.14
 signing_key: 
 specification_version: 4
 summary: Use Postgres advisory lock to isolate code execution across machines