ocean-dynamo 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1edea2a1dd072df524a42c558831b59f14044a92
-  data.tar.gz: 8186892ac7caaadc05ff76e1fc685b4066e6676c
+  metadata.gz: eccd38308405a737045ac18286f34b6c23cc2c89
+  data.tar.gz: 47afc68ac6376fbf0340545d2875cc64992a96b7
 SHA512:
-  metadata.gz: 29380a531e0f32547c377b316e707561680a0a07260584adc7ed26d48d72b688b76dc10719c0bb59cc2833198f77de671bd15657e5e9a9507a4bc7fc3edd0788
-  data.tar.gz: 9ef2050f6f9cadd6adcea44928996c43d438812dc4c1a89a7410c7a38a60d1c64befd835b7cdd41611205c5ce82e3770db2ab2570f98b08a7181942bd35bbbb7
+  metadata.gz: 0f096a9bc3e8d7e74b1412cb611abebd33472a4a93f2ed17b3340b09d31ee51a760e1a930e9f0609560c1924692e26f2115c86dc769841afec3d2a14acabf844
+  data.tar.gz: 4fcce617694af0423f12f71afef65feec00ce8c22e4c875d3e7ac9c50c08b17ce5336cb2a490a24a9563bccbb6ed69e889918a5804cb9d11139c38ccf2168255

data/README.rdoc

@@ -10,10 +10,6 @@ OceanDynamo requires Ruby 2.0 and Ruby on Rails 4.0.0 or later.
 
 ==== Features
 
-OceanDynamo will use secondary indices to retrieve related table items, 
-which means it will scale without limits. (NB: this is a pre-release which as yet doesn't
-implement relations, but they are underway.)
-
 As one important use case for OceanDynamo is to facilitate the conversion of SQL based
 ActiveRecord models to DynamoDB based models, it is important that the syntax and semantics
 of OceanDynamo's operations are as close as possible to those of ActiveRecord. This means
@@ -27,6 +23,13 @@ methods you're used to. The design goal is always to implement as much as possib
 ActiveRecord interface, without sacrificing scalability. This makes the task of switching from
 SQL to no-SQL much easier.
 
+Due to its similarity to ActiveRecord, OceanDynamo works with FactoryGirl.
+Furthermore, future versions will keep track of and delete instances after tests.
+
+OceanDynamo will use secondary indices to retrieve related table items, 
+which means it will scale without limits. (NB: this is a pre-release which as yet doesn't
+implement relations, but they are underway.)
+
 
 === Documentation
 

data/lib/ocean-dynamo/dynamo.rb

@@ -401,6 +401,13 @@ module OceanDynamo
     end
 
 
+    def valid?(context = nil)
+      context ||= (new_record? ? :create : :update)
+      output = super(context)
+      errors.empty? && output
+    end 
+
+
     def save
       begin
         create_or_update

data/lib/ocean-dynamo/version.rb

@@ -1,3 +1,3 @@
 module OceanDynamo
-  VERSION = "0.1.1"
+  VERSION = "0.1.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ocean-dynamo
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Peter Bengtson
@@ -109,22 +109,24 @@ dependencies:
       - !ruby/object:Gem::Version
         version: 0.1.3
 description: "== OceanDynamo\n\nThis is the OceanDynamo ruby gem, implementing a highly
-  scalable Amazon DynamoDB near drop-in \nreplacement for ActiveRecord.\n\nOceanDynamo
-  will use secondary indices to retrieve related table items, \nwhich means it will
-  scale without limits. (NB: this is a pre-release which as yet doesn't\nimplement
-  relations, but they are underway.)\n\nAs one important use case for OceanDynamo
-  is to facilitate the conversion of SQL based\nActiveRecord models to DynamoDB based
-  models, it is important that the syntax and semantics\nof OceanDynamo's operations
-  are as close as possible to those of ActiveRecord. This means\nthat all callbacks
-  should be available, before, around and after, and that they should be\ncalled in
-  the same order as in ActiveRecord. Ocean-dynamo follows this pattern closely and\nis
-  of course based on ActiveModel.\n\nThe attribute and persistence layer of OceanDynamo
-  is modeled on that of ActiveRecord:\nthere's +save+, +save!+, +create+, +update+,
-  +update!+, +update_attribute+ and all the other\nmethods you're used to. The design
-  goal is always to implement as much as possible of the\nActiveRecord interface,
-  without sacrificing scalability. This makes the task of switching from\nSQL to no-SQL
-  much easier.\n\nSee also Ocean, a Rails framework for creating highly scalable SOAs
-  in the cloud, in which\nocean-dynamo is used as a central component: http://wiki.oceanframework.net"
+  scalable Amazon DynamoDB near drop-in \nreplacement for ActiveRecord.\n\nAs one
+  important use case for OceanDynamo is to facilitate the conversion of SQL based\nActiveRecord
+  models to DynamoDB based models, it is important that the syntax and semantics\nof
+  OceanDynamo's operations are as close as possible to those of ActiveRecord. This
+  means\nthat all callbacks should be available, before, around and after, and that
+  they should be\ncalled in the same order as in ActiveRecord. Ocean-dynamo follows
+  this pattern closely and\nis of course based on ActiveModel.\n\nThe attribute and
+  persistence layer of OceanDynamo is modeled on that of ActiveRecord:\nthere's +save+,
+  +save!+, +create+, +update+, +update!+, +update_attribute+ and all the other\nmethods
+  you're used to. The design goal is always to implement as much as possible of the\nActiveRecord
+  interface, without sacrificing scalability. This makes the task of switching from\nSQL
+  to no-SQL much easier.\n\nOceanDynamo will use secondary indices to retrieve related
+  table items, \nwhich means it will scale without limits. (NB: this is a pre-release
+  which as yet doesn't\nimplement relations, but they are underway.)\n\nDue to its
+  similarity to ActiveRecord, OceanDynamo works with FactoryGirl.\nFurthermore, future
+  versions will keep track of and delete instances after tests.\n\nSee also Ocean,
+  a Rails framework for creating highly scalable SOAs in the cloud, in which\nocean-dynamo
+  is used as a central component: http://wiki.oceanframework.net"
 email:
 - peter@peterbengtson.com
 executables: []