> I've got a meeting coming up with a small team from a commercial DB
> vendor that's interested in extending their support into the Python
> community (yea!). Unfortunately, their analysis up until this
> point has left them with the impression that supporting the django
> ORM is the first priority, and that SQLAlchemy can come later.
> (boo!)
>
> I need some help with providing arguments on why they should switch
> their priorities.
what a DB vendor would have to do with ORM?
the DB-related layer ('engine' in SA), yes, but orm?
i'm not familiar with how thick django's layers are, maybe just try to
compare the complexities. If SA notion of DB-engine is less
complex/entangled that django's then u have a 'plus' - it would be
cheaper/easier for them to do it.
But then, it would be a manager's decision so try to think as
(marketing)manager. Which means: answer yourself the question 'where
the money is'. in both directions 'come' and 'gone'.
thumb's up
svilen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
