DY> What about unencrypted distributed databases? Should we care about DY> hiding PSQL source also from SYSDBA / DBO? Are there real cases when it DY> would be needed?
Well, the currently "hack" makes no distinction of users, so if the idea is to maintain currently behavior, it doesn't matter who is the user, he would see no source. >> 1) Create an official way to make the source null DY> So far I tend voting for (1), using a special syntax. +1, and we don't need to advertise it as a protection at all. This special syntax can be described as to be used by people who doesn't want to have the plain source code stored in the database (for whatever is the reason <g>). []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br ------------------------------------------------------------------------------ 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