On 8/30/06, David Elias <[EMAIL PROTECTED]> wrote:
>
>
> Robin Munn wrote:
> > The notes on implementation that Adrian posted pretty much match what
> > I'm thinking at this point. The plan is to make this 100% API
> > compatible (if possible -- you never know what will turn up once you
> > start implementing some idea), so that existing code doesn't need to
> > change. But if you want access to the underlying SQLAlchemy objects to
> > do something like a nine-table query involving five LEFT OUTER JOINs
> > and two subselects, well, you should be able to do that as well.
>
> Indeed great news!!
>
> At work i am trying to build the Django ORM on the top of SQLAlchemy
> core. I've tried on the top of the ORM but it was overkill, but i could
> had done something wrong. I was getting about ~10 request per second
> oposed to ~50 request per second with firebird.
>
> Are you planning to build the integration on the top of the SQLAlchemy
> ORM?
If I understand your question correctly, the answer is yes. Here's how
I plan to have it work:
User models
|
v
Django DB
| <-- This is the API I'll be building
v
SQLAlchemy ORM
|
v
Database (Postgres, SQLite, Firebird...)
The plan is for the user model to Django DB API won't change at all
(if possible), and I won't be touching the SQLAlchemy-to-database API
either. I'll be building that connector in the middle.
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0xD6497014
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
