Hi,
> Lastly, there's a change I made which seems to be a sort of kludge to me,
> but I did it to get things working. When doing the build-project.sh init,
> when inserting the tables, etc, torque generates a drop sequence or drop
> table first, before creating...on the other db's, such as mysql, there's
> a syntax for checking if the table exists (...IF EXIST...), but postgresql
> doesn't support this, and I can find no equivalent. So when SQLExec goes
> to drop, it generates an error, and ant bails out.
There are quite a few databases which don't have an equivalent to the
mysql IF EXISTS sql clause. DB2 and PostgreSQL are two of them.
> What I did to get around this is add an 'onError=continue' to the <sql>
> in build-project.xml. This seems nasty to me, as you'd like to quit
> when you run into other errors. I'm far from a postgresql expert, so
> maybe someone else has a better idea on a cleaner solution?
One possible solution is to remove the table dropping from the Turbine sql
altogether. Then if someone goes to create their tables and they already
exist, they can manually drop the offending tables themselves. I don't
really like the idea of automating table drops anyway... and I can't
think of any other solution, apart from ignoring the sql errors like John
did.
Regards,
-- Rodney
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
