sequel-pg_advisory_lock 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b48cb4023fcc88c838d6de22714b92c61437f02f
-  data.tar.gz: f0ec5d03ce435061e6a995e999b79f34c67f0dcc
+  metadata.gz: 6a40fd8d2f62e959b8f9814e0faf413e4d1b48d1
+  data.tar.gz: 5a98cb2b24085834aa948c4e344f366f6c413a89
 SHA512:
-  metadata.gz: 8adac28854b26f69ecdd2324b0ed1c76028b07b1975d5317ae46e5914044bf04d8fea57f560e247c67f0dc2ecd432364c187e08293e2af99b4d2f8c228eaa523
-  data.tar.gz: 6dd7a64a7049aeb7fba91de618224cf6a9dc6909c605228e80ba771f0f9ca8cbf95047aecf5cdd353c062ae196ee3ede5c4d433be2badbb790b41779f5efeeff
+  metadata.gz: 7123c0f44ca88d7f16057d17b66deb98d1fad6cfcb826449a7f659d30337e2c6151c4b1756cc596aa4e337ebdf1c80ef0babb956c864d25c993351d787995a6d
+  data.tar.gz: f2eb700856791db03c8c4e6f42d51144e01fe454cbf82cacabb822ff05d51cb64e65ca89f892a8beb06b1a7c6f0d6dc77999ece95dc6ad8f799ef134f0bf2a73

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+# `0.1.2` (2017-11-23)
+
+* Update gem documentation and summary.
+
 # `0.1.1` (2017-11-22)
 
 * Update gem summary.

data/README.md

@@ -1,8 +1,8 @@
 # sequel-pg_advisory_lock [![Build Status](https://travis-ci.org/yuryroot/sequel-pg_advisory_lock.svg?branch=master)](https://travis-ci.org/yuryroot/sequel-pg_advisory_lock)
 
 Gem `sequel-pg_advisory_lock` is an extension for ruby [Sequel](https://github.com/jeremyevans/sequel) library 
-that helps using [PostgreSQL advisory locks](https://www.postgresql.org/docs/9.6/static/explicit-locking.html#ADVISORY-LOCKS)
-in your application.
+that allows using [PostgreSQL advisory locks](https://www.postgresql.org/docs/9.6/static/explicit-locking.html#ADVISORY-LOCKS)
+for application-level mutexes.
 
 ## Installation
 
@@ -47,13 +47,15 @@ It's also possible to specify different function in second parameter of `registe
 DB.register_advisory_lock(:my_lock, :pg_try_advisory_lock)
 ````
 
-All supported lock functions are described in [here](#available-types-of-locks). 
+All supported lock functions are described [here](#available-types-of-locks). 
 
 Finally, you can use registered lock:  
 
 ```ruby
 DB.with_advisory_lock(:my_lock) do
-  # do something 
+  # do something
+  # this block works like application-level mutex, 
+  # so code inside block is protected from concurrent execution 
 end
 
 ``` 
@@ -62,7 +64,9 @@ An optional *4-bytes integer* parameter can be passed to `with_advisory_lock` me
 
 ```ruby
 DB.with_advisory_lock(:my_lock, 1) do
-  # do something   
+  # do something
+  # this block works like application-level mutex, 
+  # so code inside block is protected from concurrent execution 
 end
 
 ```

data/sequel-pg_advisory_lock.gemspec

@@ -4,11 +4,11 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = 'sequel-pg_advisory_lock'
-  spec.version       = '0.1.1'
+  spec.version       = '0.1.2'
   spec.authors       = ['Yury Shchyhlinski']
   spec.email         = ['Shchyhlinski.YL@gmail.com']
 
-  spec.summary       = "#{spec.name} is an extension for ruby Sequel library that helps using PostgreSQL advisory locks in your application"
+  spec.summary       = 'Extension for ruby Sequel library that allows using PostgreSQL advisory locks for application-level mutexes.'
   spec.homepage      = "https://github.com/yuryroot/#{spec.name}"
   spec.license       = 'MIT'
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: sequel-pg_advisory_lock
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Yury Shchyhlinski
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-11-21 00:00:00.000000000 Z
+date: 2017-11-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sequel
@@ -125,6 +125,6 @@ rubyforge_project:
 rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
-summary: sequel-pg_advisory_lock is an extension for ruby Sequel library that helps
-  using PostgreSQL advisory locks in your application
+summary: Extension for ruby Sequel library that allows using PostgreSQL advisory locks
+  for application-level mutexes.
 test_files: []