Ask Your Question
1

MYSQL issue with migration 22 on install [fixed]

asked Nov 01 '10

graeme gravatar image graeme
307 1 4 11
http://investmentqa.com/

updated Nov 01 '10

Evgeny gravatar image Evgeny flag of Chile
6665 31 49 95
http://askbot.org/

manage.py migrate askbot gives the following error:

_mysql_exceptions.ProgrammingError: (1146, "Table 'graeme_investmentqa.pg_language' doesn't exist")

I managed to install by only migrating up to migration 21. This seems to be an acceptable workaround for the moment - at least it seems to work (I have some issues, but they are probably extra config needed for my host).

Also, the documentation does not mention that you also need to migrate askbot.deps.django_authopenid

1 Answer

Sort by ยป oldest newest most voted
0
graeme has selected this answer as correct

answered Nov 01 '10

Evgeny gravatar image Evgeny flag of Chile
6665 31 49 95
http://askbot.org/

Thanks, fixed this. Next time the migration 22 will work (it will actually be a do-nothing) for MySQL as it should.

link

Comments

Thanks Evgeny. You are very helpful and you seem to fix problems very fast. Askbot is very easy to install (I used pip install in a virtualenv). The docs could be improved, but they are better than whats available for the alternatives. graeme (Nov 01 '10)
Graeme, you are welcome. Feel free to ask if you have any issues with your site or suggestions. Evgeny (Nov 01 '10)
I'm installing askbot 0.6.79 with MySQL (MyISAM). Migration 22 is still failing. I see that there is a condition in the migration code to only apply to postgresql. But, may be it is still expecting to see the pg_language table? Error: .../MySQLdb/connections.py", line 36, in defaulterrorhandler django.db.utils.DatabaseError: (1146, "Table 'askbot.pg_language' doesn't exist" codedigger (Apr 26 '11)
Your setting DATABASE_ENGINE must be incorrect..... no? Is it "mysql" or "postgresql_psycopg2"? With "mysql" this migration must pass through without doing anything. Evgeny (Apr 26 '11)
OK, that was the problem! Even through I override settings.py with my settings_local.py with DATABASES = {...}, I guess DATABASE_ENGINE is a DIFFERENT setting, so it worked as far as db connection goes, but the migration script was still picking up DATABASE_ENGINE. Now all migrations worked. Thanks! codedigger (Apr 26 '11)
see 1 more comment

Your answer

Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
[hide preview]

Question tools

Follow

subscribe to rss feed

Stats

Asked: Nov 01 '10

Seen: 42 times

Last updated: Nov 01 '10