completely agree ; becoming a promotional tool for an ORM
may not be worth the little pain of learning sql.
On Tue Oct 3 4:40 , [EMAIL PROTECTED] sent:
Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
> java system just traverses its contents and stores the associated objects.
Hmm, hope you've got lots of RAM ;-)
> FYI, the mapping from the user concept of an appointment system to the basic
> computer
[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
