James Bennett wrote: > On 8/22/06, Karl Guertin <[EMAIL PROTECTED]> wrote: > > http://www.sqlalchemy.org/docs/adv_datamapping.myt > > Some of these examples deal with rather exotic use cases that, I > think, are close to the edge of what ORM can reasonably do before the > abstraction starts leaking. > > The "map multiple tables to an object", for example, really feels like > something that'd be better handled by a view at the database level.
Yes, a lot of things would be better handled at the database level, e.g., inheritance, views, more advanced validation, but it would break database independence. I guess there's more than a few people running MySQL/PostgreSQL as their production and development database, but SQLite (:memory:) as their testing database. > It's something to think about though; if you've got ideas for concrete > implementations that would satisfy relatively common use cases, please > do submit tickets for them. It's unfortunately beyond me. These things are presumably quite hard to get right, and that's why I use a framework. What's a bit dangerous is that I do feel a bit let down if the framework oversold itself in this respect when I 3 months down-the-road discover it couldn't do what I need (thus the rants about "it's all marketing"). To me, what Django got right is a coherent set of core components that work well and feel right together, and that's extremely important. They're not individually "best of breed", but they don't feel as frankensteinish together as some of the other frameworks' components. This is also, btw, what Ruby on Rails got right initially; over time the components improved, and they're now really good. All we need is involvement of experts for each of the tricky components :( I'll add another thing to the wish-list for the framework: database schema/data migration. Rgds, Bjorn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
