On Wed, Feb 3, 2010 at 11:02 PM, Klemens Mantzos
wrote:
> thx!
>
> syncdb is now calling the database router before actually syncing to
> the db. but...
>
> ...stumbled upon a new problem:
>
> if i do
> python manage.py syncdb --database=default
> before i sync the users database this error comes
@klemens you are most definitely not alone.
I made a router that would allow me to have one database per app and I
get exactly the same type of error on both postgres and sqlite. Doing
syncdb on the default db work as it should but when I in this case do
a ./manage.py syncdb --database=ads I get th
thx!
syncdb is now calling the database router before actually syncing to
the db. but...
...stumbled upon a new problem:
if i do
python manage.py syncdb --database=default
before i sync the users database this error comes up (which seems ok to me):
django.db.utils.DatabaseError: (1146, "Table
'm
On Mon, Feb 1, 2010 at 11:07 PM, Klemens Mantzos
wrote:
> hi list,
>
> checked out the new multidb feature
> (http://docs.djangoproject.com/en/dev/topics/db/multi-db/).
>
> i assumed that syncdb would only sync those models in the database
> when calling allow_syncdb() of the database routers retu
hi list,
checked out the new multidb feature
(http://docs.djangoproject.com/en/dev/topics/db/multi-db/).
i assumed that syncdb would only sync those models in the database
when calling allow_syncdb() of the database routers return True. is
that true?
my problem: syncdb syncs the complete model i
5 matches
Mail list logo
