I got errors returns from the email server so I'm re-sending: Jim, your latest posting does not help the current situation. It only complicates the discussion unnecessarily.
The immediate problem, and the only one that needs immediate discussion on this list, is how to re-instate the functionality in the initial release of FB3. The problem was identified early enough that a quick fix can be made. The justification has been made that it is needed. All that is needed *right now* is a decision on which solution to provide. Therefore the vote should continue. You recent post is more appropriate for the architecture list. It conflates the immediate problem with a larger problem. The larger problem is how to provide application developers a way to protect part of their application which is stored as data in the database from the prying eyes of database users. That, in turn, is part of an even larger problem of how to protect *any* data stored in the database from prying eyes. But the immediate problem is how to prevent FB3 from being released with reduced functionality that will create problems for the current developer community. The solution can be short term. But it is important to get on with a solution s the release schedule is not delayed unduly. Discussion of the larger issues can be done afterwards. On the architecture list. ------------------------------------------------------------------------------ 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
