here's the code in it:
for model in created_models: db_table=model._meta.db_table if db_table not in skip: skip.add(db_table) engine = storage.get(model._meta.db_table,default_storage) stmt = 'ALTER TABLE %s ENGINE=%s' % (db_table,engine)
Add some debug statements to see which tables are actually being altered. If its trying to alter the test_* tables, they obviously wont be there, because theyre created only while running the tests...
The fix mite be as simple as putting the test_ tables in the skip set.
-
Suraj Jacob
-- On Thu, Oct 28, 2010 at 14:56, girish shabadimath <girishmss.1203@gmail.com> wrote:
Hi all,im re-sending this mail, am i missing any thing here?im using django 1.2there are two databases involved in my project (default and XYZ (used only for migration))i use a consistant MySQL storage type for all apps, all models (including m2m).This is done by registering a post-syncdb signal in management.py file which converts all tables to innodb.(code partially taken from: http://code.djangoproject.com/wiki/AlterModelOnSyncDB )(Description of management.py magic is at http://code.djangoproject.com/wiki/Signals)i wrote few tests for one of my application,when i run ./manage.py test following error occurs:DatabaseError: (1146, "Table 'test_XXX.django_content_type' doesn't exist")any clues?--
Girish M S
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment