:( Guess I'll have to move to the city.
Anyway, yes: it is kind of hard.
Think about it:
You have a huge table, you add a column, which updates all rows in
column to have a value.
If you have no default and the column is NULL(able), then the update is
to all NULL values.
If you have a defaul
Hello Lorna,
you have lost your farm: Postgresql does support this! :-)
I.e. with Postgresql you can manipulate ddl within every transaction and roll
back the whole transaction if an error occurs.
This is a truely professional feature. Even more: If you have to manipulate
your ddl often (in produ
Yes Campbell, the enhancement you suggest is being implemented for 1.8.0
Fred
- Original Message -
From: "Lorna Burnet" <[EMAIL PROTECTED]>
To:
Sent: 12 March 2005 22:24
Subject: Re: [Hsqldb-developers] Transaction Commit
It happens because in hsqlsb, currently,
It happens because in hsqlsb, currently, data definition language execution is
not "transactional"
That is, you cannot roll back table creation, etc.
So, if you issue ddl in the middle of a transaction, this is equivalent to an
implicit commit.
The same is true of many DBMS, including Oracle,
