The problem is what is considered a table change. What about changing the precision of a column? I'm aware of a (closed source) DB engine which changes the order of columns for some precision changes (namely when the new type takes up more bytes than the old one) but keeps it the same for the rest.
map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
| [reply]
[d/l] |
The problem is what is considered a table change.
Yes, that's a good point - over in my other replies I've been arguing against SELECT * anyway. I just felt that saying it was "unspecified" was, well, too unspecific :-)
| [reply]
[d/l]
[select] |
