James Starkey wrote:
> Excuse me, but the requirement is to make the source
> unreadable. Carlos listed five ways this could be done.
> I came up with a sixth that is less code, less instrusive,
> and more general than the others, and you say it is
> unhelpfull. Why is this?
[...]
I'm in no position to make an assessment of this, but I am
curious about your claims of "less code, less intrusive".
That might be true of one or two of the other options, but
options 1 and 4 would seem inherently simpler. My vote in
this doesn't really count (I'm not a developer and I don't
use this requested "feature") but it seems that both options
1 and 4 have the advantage of being familiar to those that
are already doing this (so, hopefully, easy for them to
adapt to as they update to v3.0). Any of the other options,
and yours in particular, will require a significant change
in their current code and implementation procedures.
At this late stage of v3.0, it seems to me that simple and
least possible change (to v3 and to the developer) should
be high on the list of priorities. More sophisticated
options could be assessed in detail later. Personally
(assuming it's not more difficult than it sounds) I think
that option 4 ("Leave the rdb$procedures and rdb$triggers
writable (or at list the source field)") is the best fit
at this time.
--
Geoff Worboys
Telesis Computing Pty Ltd
------------------------------------------------------------------------------
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
