"*manual* orm mapping" , I mean doing the sql manually.
I think a generalized ORM layer isn't really needed unless youre going
to do lots of throwaway databases, as you might need for some
user feedback handling public web site , which from interview movie
posted earlier, is what django was for , some mass media/ interactive advertising
web site .
Wonder if these ORMs do database versioning well e.g.
you change your object definitions, and it generates ALTER TABLE
statements to match.
On Tue Oct 3 4:40 , [EMAIL PROTECTED] sent:
[snip]
> the particular day and provider. After that, you can just do straight
> forward manual
> object relational mapping, if you want it stored in a sql relational
> database.
The problem I have with ORMs is how you map queries, especially joins,
to object space. RoR does this fairly well, and also (and more importantly)
let's you use SQL for the WHERE clause when required, with a minimum of fuss.
The Python ORMs try very hard to map everything to Python, with various neat
tricks, but it's still harder than writing a little SQL.
Ian
_______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
