Timeline for Why won't some DBMS's allow rollback for certain DDL statements?
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2011 at 22:32 | comment | added | Gary | As an aside, the 11gR2 version introduces the concept of Editions to assist with hot upgrades. Effectively existing connections use one edition (with five columns). You start a new edition, add a column and start some new connections using the new edition for new sessions. Once all outstanding sessions are finished, the old edition is cruft and everything uses the new edition. No rollback, but you don't put new activity on your new edition until its all working. | |
| Jan 25, 2011 at 21:37 | comment | added | Gaius | Interesting you should say that, I had a similar kind of issue the other day, the application was supposed to be "hot" deployable, but changing the table structure for the new version, it had no way to recompile JDBC PreparedStatements apart from restarting it, so much for that! | |
| Jan 25, 2011 at 21:03 | history | answered | Gary | CC BY-SA 2.5 |