passive_record 0.4.3 → 0.4.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 40a7223415652b0909737104ce89ef4b217ea868
-  data.tar.gz: 6c12988254b55576d5233dc5342efb57885d980d
+  metadata.gz: 3bbf676f1d3d94dce7e4b0b0d2faa89476149335
+  data.tar.gz: c1607589beb7a3f7cf199cf1f8bdaf67b12568bc
 SHA512:
-  metadata.gz: a7ace663d5d19795a44d2db854dbfb1d927d5f17b3f846efe2d7c8e6d360a99339f83045a12c041cadb85426fd3166230b08218dbb84a309d58047780bf1c202
-  data.tar.gz: 472bc65c4d271b5ee23913163734f1434b45948e7f78331dd55a33c2994cb16449c421bd32c5e1ce42ee42e2d256f1fe04affa8d64e139e95ced64ab578e1253
+  metadata.gz: 158a69a9f39cb6cd8df9dae55f2a4554498af25d3044c94d3f1b3af69ed7ee810891efa365470ebb95fddfe151de963d8aa9abc94066638f46ee47259af44acd
+  data.tar.gz: 23c5791750f524c311a0e98f3849e7b399f28c883b174635289eb25d1ccfa09662c6b35d4c103d18f18321471feb6579465e9998db66e7ab2edb34232194cf0a

data/README.md

@@ -112,9 +112,9 @@ PassiveRecord may be right for you!
   - `User.destroy_all`
   - `User.each` enumerates over `User.all`, giving `User.count`, `User.first`, etc.
   - `User.find(id_or_ids)`
-  - `User.find_by(name: 'Aloysius')`
-  - `User.find_all_by(job: ['manager', 'developer', 'qa'])`
-  - `User.where(birthday: 1.day.ago...1.day.from_now)` (returns a `PassiveRecord::Query` object)
+  - `User.find_by(conditions)`
+  - `User.find_all_by(conditions)`
+  - `User.where(conditions)` (returns a `PassiveRecord::Query` object)
 
 ### Belongs To
 
@@ -199,7 +199,8 @@ PassiveRecord may be right for you!
 # Prior Art
 
   - Approaches exist that use ActiveRecord directly, and then override various methods in such a way to prevent AR from trying to persist the model. The canonical example here is the [tableless model](http://railscasts.com/episodes/193-tableless-model?view=asciicast) approach, and the use case given there is a model that wraps around sending an email. This is maybe interesting because, similar to the round-trip with a database, sending mail is externally "effectful" (and so, for instance, you may wish to take additional care around confirmation or retry logic, in order ensure you are not sending the same message more than once.)
-  - These approaches are seen as somewhat hacky today, given that [ActiveModel](https://github.com/rails/rails/tree/master/activemodel) can give plain old Ruby objects a lot of the augmentations that ActiveRecord gives, such as validations, hooks and attribute management. However I don't really see a way to do relations that interoperate with ActiveRecord the way you could, at least to some degree, with tableless models.  - It's not really clear to me yet if it's interesting for PassiveRecord to be able to interoperate smoothly with ActiveRecord relations. It seems like we might be able to pull some similar tricks as the "tableless" approach in order to permit at least some relations to work between them.  But their intentions are so different I can't help but think there would be very strange bugs lurking in any such integration -- so the encouraged architecture would be a complete separation between active and passive models.
+  - These approaches are seen as somewhat hacky today, given that [ActiveModel](https://github.com/rails/rails/tree/master/activemodel) can give plain old Ruby objects a lot of the augmentations that ActiveRecord gives, such as validations, hooks and attribute management. However I don't really see a way to do relations that interoperate with ActiveRecord the way you could, at least to some degree, with tableless models.  
+  - It's not really clear to me yet if it's interesting for PassiveRecord to be able to interoperate smoothly with ActiveRecord relations. It seems like we might be able to pull some similar tricks as the "tableless" approach in order to permit at least some relations to work between them.  But their intentions are so different I can't help but think there would be very strange bugs lurking in any such integration -- so the encouraged architecture would be a complete separation between active and passive models.
 
 ## Copyright
 

data/lib/passive_record.rb

@@ -1,4 +1,4 @@
-require 'ostruct'
+require 'forwardable'
 
 require 'active_support'
 require 'active_support/core_ext/string/inflections'

data/lib/passive_record/version.rb

@@ -1,4 +1,4 @@
 module PassiveRecord
   # passive_record version
-  VERSION = "0.4.3"
+  VERSION = "0.4.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: passive_record
 version: !ruby/object:Gem::Version
-  version: 0.4.3
+  version: 0.4.4
 platform: ruby
 authors:
 - Joseph Weissman
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-04-02 00:00:00.000000000 Z
+date: 2016-04-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -185,7 +185,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.6
+rubygems_version: 2.4.8
 signing_key: 
 specification_version: 4
 summary: no-persistence relational algebra