entitymap 0.0.1 → 0.0.2

data/Changelog

@@ -0,0 +1,7 @@
+0.0.2: 2012-02-12
+
+* Bug fix: the included added an entity attr_accessor to target object
+
+0.0.1: 2012-02-12
+
+* Initial release (Entity created for objects for which EntityMap is included)

data/README.md

@@ -1,43 +1,45 @@
 # EntityMap
 
-The concept is to have an in-memory entity-relationsip model that has unique and
-unambiguous mapping of the (business) entities and the relationships between them,
-but still closely linked to the SQL concept of a foreign key as unambiguous
-implementation of a relationship between tables).
+The idea is to have an in-memory entity-relationsip model that has unique and
+unambiguous mapping of the (business) entities and the relationships between
+them. On the other hand, the lowest level will be limited to the simple concept
+of a foreign key/pointer from one entity to another, as an unambiguous
+implementation of an asymmetric relationship between two entities.
 
 In ActiveRecord, there is an IdentityMap being developed, but even with
 IdentityMap turned on, the belongs_to and has_many relationships between
 Parent and Child are not uniquely mapped to each_other. It is possible to
 have at the same time
 
-``
+```ruby
 daisy.children # => [#<Child:0x9275fe8 @name="Peter">]
 peter.mother # => #<Mother:0x964c518 @name="Maria">
 ```
-If I am the child of Daisy, then she should be my mother, huh ...
+If I am the child of Daisy, then she should be my mother, no?
 
 So, the focus is on unambiguous and easy use of the relationships
 in an ER model (Entity-Relationship model) where the reciprocity
-of the 2 directions of the relationship is guaranteed correct.
+of the view on the 2 directions of the _same_ relationship is
+guaranteed correct.
 
 Mapping this form of ER-model to a database as a persistence
-layer is a second priority, after establishing the correct
+layer is a different aspect, after establishing the correct
 Entity and Relationship behavior.
 
 ## Feature wish list
 
-it "handles belongs_to - has_many atomically in 1 place"
-it "has identity_map for entities"
-it "can be persisted in 1 command"
-it "will check validations on _all_ entities before persisting"
-it "allows select list in a form to work cleverly"
-it "has 'live' scopes that are honored in memory"
-it "can be marshalled"
-it "works with a Plain Old Ruby Object"
-it "works with other ORMs (ActiveRecord, Sequel, Datamapper)"
-it "works with SimpleForm 2"
-it "works with JRuby"
-it "works in other languages (Java, ...) ?"
+* it "handles belongs_to - has_many atomically in 1 place"
+* it "has identity_map for entities"
+* it "can be persisted in 1 command"
+* it "will check validations on _all_ entities before persisting"
+* it "allows select list in a form to work cleverly"
+* it "has 'live' scopes that are honored in memory"
+* it "can be marshalled"
+* it "works with a Plain Old Ruby Object"
+* it "works with other ORMs (ActiveRecord, Sequel, Datamapper)"
+* it "works with SimpleForm 2"
+* it "works with JRuby"
+* it "works in other languages (Java, ...) ?"
 
 ## Usage Example
 
@@ -97,15 +99,13 @@ peter.father.father_of # => [#<Child:0x9275fe8 @name="Peter">, #<Child:0xa49e030
 # adding an implementation of persistence
 
 class Child
-  # not sure if this is enough ActiveRecord
-  include ActiveRecord::Persistence
-  include ActiveRecord::FinderMethods
+  include ActiveRecord::Model
+  include EntityMap
 end
 
 class Parent
-  # not sure if this is enough ActiveRecord
-  include ActiveRecord::Persistence
-  include ActiveRecord::FinderMethods
+  include ActiveRecord::Model
+  include EntityMap
 end
 
 EntityMap.save # => true #(O)
@@ -113,12 +113,11 @@ peter.id # => 1 #(P)
 jan.id # => 2
 new_peter = Child.find(1)
 peter.object_id == new_peter.object_id # => true #(Q)
-peter.ref == new_peter.ref # => true #(R)
 ```
 
 ## Example of the Parent-Child ambiguity in ActiveRecord (4.0.0.beta)
 
-```
+```ruby
 peterv@ASUS:~/b/github/rails/rails/new_app$ cat app/models/*
 class Child < ActiveRecord::Base
   belongs_to :parent, :inverse_of => :children

data/lib/entity_map/included.rb

@@ -1,7 +1,5 @@
 module EntityMap
 
-  attr_accessor :entity
-
   def initialize
     entity = Entity.new(self, EntityGroup.single)
     super

data/lib/entity_map/version.rb

@@ -1,3 +1,3 @@
 module EntityMap
-  VERSION = "0.0.1"
+  VERSION = "0.0.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: entitymap
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,11 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-02-11 00:00:00.000000000 Z
+date: 2012-02-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
-  requirement: &72628490 !ruby/object:Gem::Requirement
+  requirement: &82065520 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -21,7 +21,7 @@ dependencies:
         version: '0'
   type: :development
   prerelease: false
-  version_requirements: *72628490
+  version_requirements: *82065520
 description: ! 'Mapping entities and relations atomically in memory during the
 
   processing of a business transaction.
@@ -37,6 +37,7 @@ extra_rdoc_files: []
 files:
 - .gitignore
 - .rspec
+- Changelog
 - Gemfile
 - MIT-LICENSE
 - README.md