stephane.ducasse at free.fr
Mon Apr 7 17:28:52 UTC 2008
still it would be good to have a layer on top of Glorp, I'm amazed by
of code we should write (See HPI seaside tutorial). It would be good
that a reflective or meta
description approach would be proposed by default and that if people
want to have something that can
do it (as it is now). I do not see the value of paying in advance
functionality I do not need.
Glorp start up is too high from my perspective (I'm lazy and proud of
On Apr 3, 2008, at 6:37 AM, Randal L. Schwartz wrote:
>>>>>> "Rob" == Rob Rothwell <r.j.rothwell at gmail.com> writes:
> Rob> Has anyone written anything like the ActiveRecord for Glorp?
> Using something like ActiveRecord for Glorp would be like buying an
> just to taxi around the airport without ever lifting off the ground.
> The big plus in Glorp that I'm seeing is that you can do more than
> DirectMapping... you can describe tables on one side, model-objects
> on the
> other, and then produce an almost arbitrary mapping between the two.
> Sure, for simple stuff, one-class-is-one-table might make sense, but
> attention to the other kinds of mapping styles. Lots of power in
> there. It's
> how an ORM *should* be done.
> Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503
> 777 0095
> <merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
> See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl
> Beginners mailing list
> Beginners at lists.squeakfoundation.org
More information about the Beginners