stephane.ducasse at free.fr
Mon Apr 7 17:30:00 UTC 2008
I totally agree. Upfront vs practical.
For my dead stupid data I want a dead stupid way of storing them in
On Apr 3, 2008, at 7:57 AM, Ramon Leon wrote:
>> Sure, for simple stuff, one-class-is-one-table might make
>> sense, but pay 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. -
> Rails has made it pretty clear that *most* apps really are that
> simple since
> it only supports direct mapping. Glorp is absurdly powerful in its
> to map objects to tables, *assuming* that mapping is the correct
> answer of
> course. As powerful as Glorp is, most people will end up spending a
> lot of
> time wrestling with mappings, probably far more than they want.
> Glorp is an
> expert framework for experts, but those who don't grok mapping
> patterns in
> general will be baffled by it.
> Rob, if you don't need to scale too big, check out the SandstoneDb
> on SqueakSource, it should be familiar to anyone who likes
> Ramon Leon
> Beginners mailing list
> Beginners at lists.squeakfoundation.org
More information about the Beginners