02.09.2014 01:23, Jim Starkey wrote: > >> Whatever user application that works with the database and executes >> metadata upgrade scripts itself, without invoking ISQL. > > Do you really think there are any? Seriously? Really?
I know that. Also, there are popular ISQL replacements like IBEScript. >> Option (1) from the list of solution being discussed, i.e. new DDL >> statement. > > You just argued that changing scripts was a bad idea. I argued that changing / recompiling the application was a bad idea. Changing the script is a not a problem. >> We may allow *only* setting rdb$source to NULL and *only* for SYSDBA / >> DBO, everything else will still be prohibited. > > This sounds like a whole raft of conditions. Would it have to be a literal > null or would a null input parameter be ok? How about an express that turns > out null? In VIO, NULL is just NULL, whatever is looked like at the SQL level. > What if somebody tried to set it to something other than null? An exception: > rdb$cantsetfieldtoanythingbutnullandthenonlyifyoursysdba? Throw the current exception (cannot modify system table or alike). > And how about an empty but not null blob? We may allow that, but I'd rather have it rejected either (for simplicity sake). > I gotta say that a table that has only one field writable and then only > assignable to null and only if the user is SYSDBA is a pretty crude hack. Not > quite elegant. Agreed wholeheartedly. The point was that it restores exactly what was possible prior to v3 without compromising the system tables protection and that it's easy (if not easiest) to implement. I didn't pretent it looking elegant. Dmitry ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
