On Thu, 27 Jan 2005 19:38:44 +0100, PA <[EMAIL PROTECTED]> wrote:
> 
> On Jan 27, 2005, at 19:20, Jim Barrows wrote:
> 
> > I'm speaking of frameworks that do a lot of the work for you, which
> > Rails seems to.
> 
> Hmmm... ok... so when you say that, and under some circumstances, "CRUD
> direct mapping doesn't work" you barely implies that direct mapping of
> database record to what someone calling himself "Martin Fowler" call
> "Active Record" is not a 100% solution as far as your experience goes?
> 
> http://www.martinfowler.com/eaaCatalog/activeRecord.html
> 
> Which is what RoR does in its own way:
> 
> http://wiki.rubyonrails.com/rails/show/ActiveRecord
> 
> Of course, if you simply forget about "record" and think in terms of
> "object" (ActiveObject perhaps?), all is well in the kingdom, right?

Record/Object are sort of the same.  A record might have an array as
part of it which would be implemented as a seperate table.  MIght not.
Even then, when you start looking at things as full object graphs, the
way you do htem in OO is  not the same.  Deleting an object from a
database is not synonomous with deleting an object from an object
graph.   If I change a field in an object, I can have side effects as
I change the state of the object.  Is this an Update?  is this an
Update with triggers?  How do I ripple this change through the
database?
While all of the quesitons have answers, my point is that they aren't
just simple CRUD.

> 
> Also, I fail to quite see what any of this as to do with either Struts
> or Tapestry in the first place... does Struts or Tapestry concern
> themselves directly with such mundane persistency issues? I was under
> the impression that no, they don't. Did I miss something?

Nope neither Struts nor Tapestry do that. 

> 
> Cheers
> 
> --
> PA, onnay equitursay
> http://alt.textdrive.com/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
James A Barrows

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to