Done, it's
http://code.djangoproject.com/ticket/3644
A patch is included.
Ciao, Marc.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develope
Please add them to Trac, as it's a good idea to keep an eye on them.
There's a few multi-db bugs/patches out there, e.g.:
http://code.djangoproject.com/ticket/3613
http://code.djangoproject.com/ticket/3301
If one of the trac-admins can add a multi-db value to the "version"
field in Trac, that wo
I just installed the multi-db branch yesterday and I think it is
something that surely must be supported, and I'll play more with it
the coming time. I have a simple schema-evolution idea that does not
alter existing tables, but simply copies data to new tables in another
database. Don't know if
are you using postgres? if so, when this happens again try typing:
$ ps aux | grep postmaster
do you see more than one process saying something to the effect of
"waiting for transaction?"
you may have created a deadlock (i.e. transaction2 trying to operate
on a locked row, but transaction1 wait
I've currently uncovered two bugs so far with this branch... but am
unsure where to go to enter them in for tracking. I've got a ton of
stuff working, and these popped up when I was trying to do a few
complicated things.
1. If you are doing a someclass.objects.filter and use a
select_related
I've added a nice document on how to get a project up and running with
multiple-db-branch on the wiki page.
I'd be interested in eventually maintaining the code...or helping to
maintain the code...but one of the main reasons I hadn't looked too
much into it is that I'm under a big deadline right
On 2/27/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> Documentation: no big feature can be added without complete
> documentation. In particular, a section needs to be written describing
> how the change affects existing code, and what the upgrade path (if
> any) is.
The docs have been start
On 2/27/07, Alexander Solovyov <[EMAIL PROTECTED]> wrote:
> So I have question - what needs to happen for merging this branch into
> trunk? I read page on wiki (MultipleDatabaseSupport) and examined that
> all features are completed but the docs absent in all. So writing docs
> will cause to mergi
Hi all.
Few minutes ago I drop mail to Jason Pellerin and he tolds me that he
can't maintain branch due to lack of time.
So I have question - what needs to happen for merging this branch into
trunk? I read page on wiki (MultipleDatabaseSupport) and examined that
all features are completed but t
