Ulrich Telle wrote:
In case of a SELECT statement the situation is still more complex. The
SCHEMA error could happen after reading several result rows. If you would
then redo the query automatically it would start from scratch delivering the
already read rows again. If your application code gathers the result set in
an array for example you would get duplicate rows.
I think that a DB schema change can't happend while a transaction
(explicit or implicit) is being executed.
So it's no possible that a "select * from table" fails for a shema error
while you didn't closed the query..
Paolo
