Re: [ANN] Moe - a simple database persistency framework and a few other things

On Thu, Jul 16, 2009 at 9:37 AM, Mariano Martinez Peck < marianopeck(a)gmail.com&gt; wrote: Its not different. It *uses* Roe. Roe is the the framework that talks to a postgres db (generates the SQL). MAMappedObject in Magritte-Roe connects Magritte to Roe. You implement #tableName on the class side of your model. and send #sqlColumnName: in the descriptions of the fields you want to store in the db. Then you store the object in the db by sending #save. Moe builds on these two building blocks. It lets you describe objects within objects that you want to persist to the db, and then persists them by storing integer ids only. Those embedded objects are expected to be stored in another table and can be loaded into the containing object using the contained object's id. Disadvantages: The persisted objects must be subclasses of MOEmbeddedObject that is one downside. Also you cannot recursively embed objects. This kind of thing can be insidious so you have to be careful with what you describe as an embedded object/collection. Moe is only meant to make the db mirror your application data. Redundant storage only. It's very simple. Advantages: Its *very* simple :) No way. That looks pretty awesome, though. I have to check it out.. Thanks Mariano BTW it could use a few more tests :) -- http://jmck.seasidehosting.st