On 7/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Just a small correction... multi-db is not a Summer of Code project,
> just a regular old nobody's-paying-me-to-do-it project. :)
Sorry about that. The scope and timing of it made me think it was. :-/
--~--~-~--~~
Just a small correction... multi-db is not a Summer of Code project,
just a regular old nobody's-paying-me-to-do-it project. :)
JP
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
On 7/16/06, Bryan Kyle <[EMAIL PROTECTED]> wrote:
> This solution seemed to be only half a solution. While the solution
> will work for applications that only need to connect to one database at
> a time, it will not work for me where I need to have multiple
> connections (for multiple documents)
On 7/16/06, Bryan Kyle <[EMAIL PROTECTED]> wrote:
> This solution seemed to be only half a solution. While the solution
> will work for applications that only need to connect to one database at
> a time, it will not work for me where I need to have multiple
> connections (for multiple documents)
Hi All,
I'm interested in pulling the ORM out of Django so that I can use it in
a multi-document client application.
Since starting my search for information about modularizing the ORM
out, I came across Ticket 1321
(http://code.djangoproject.com/ticket/1321). Reading through the
ticket lead me
