Revision history [back]
This is because of the newer version of postgres, I will try to find a fix for this today.
Right now you can do the following:
take a look into file askbot/search/postgresql/thread_and_post_models_01162012.plsql,
Find all instances of CREATE OR REPLACE FUNCTION and right before that line add: DROP FUNCTION IF EXISTS <funcname>; (where <funcname> is name of the function being created) then rerun the migrations.
With postgresql migrations run inside transactions, and if one fails - nothing bad happens, you are just stuck at a previous migration. In some other databases, where transactions are not supported, a broken migration can leave the database in an inconsistent state, so postgres is a good choice.
Please let me know if it helps. I will today test the same on postgres 8.3.
What OS distribution are you using?
This is because of the newer version of postgres, I will try to find a fix for this today.
Right now you can do the following:
take a look into file askbot/search/postgresql/thread_and_post_models_01162012.plsql,
Find all instances of CREATE OR REPLACE FUNCTION and right before that line add: DROP FUNCTION <funcname> IF (where EXISTS <funcname>;EXISTS;<funcname> is name of the function being created) then rerun the migrations.
With postgresql migrations run inside transactions, and if one fails - nothing bad happens, you are just stuck at a previous migration. In some other databases, where transactions are not supported, a broken migration can leave the database in an inconsistent state, so postgres is a good choice.
Please let me know if it helps. I will today test the same on postgres 8.3.
What OS distribution are you using?
This is because of the newer version of postgres, I will try to find a fix for this today.
Right now you can do the following:
take a look into file askbot/search/postgresql/thread_and_post_models_01162012.plsql,
Find all instances of CREATE OR REPLACE FUNCTION and right before that line add: DROP FUNCTION <funcname> IF EXISTS; (where then rerun the migrations.<funcname> is name of the function being created)
With postgresql migrations run inside transactions, and if one fails - nothing bad happens, you are just stuck at a previous migration. In some other databases, where transactions are not supported, a broken migration can leave the database in an inconsistent state, so postgres is a good choice.
Please let me know if it helps. I will today test the same on postgres 8.3.
What OS distribution are you using?