>Sorry Michel, but you can't. I went through this a couple of months ago. The only way is to drop the table and recreate it. So, instead of your script issuing DELETE FROM CT_PRIORITY, have your script DROP TABLE CT_PRIORITY and then CREATE TABLE CT_PRIORITY...

It's a nice workaround.

>Not exactly elegant, and it obviously shouldn't be done while the database is in use since Murphy's Law says someone will try to hit the table exactly between the DROP and the CREATE!

It's in development stage only.