Subject | protecting SP & trigger code from being viewed |
---|---|
Author | juara purba |
Post date | 2004-02-20T06:33:25Z |
hi all,
first of all, please forgive me if this topic has been discussed before...
i made an CS application using FB and before give it to customer, i would like my app(client side) be able to strip all the SP & Trigger source code from the database, leaving only the compiled BLR ( and customer data) .
Is is possible to do such thing? , i've searched IB6 doc especially on Data Definition Guide with no success.
Also reading and digging FB 1.5 RC8 release notes (the first commandment/rules to do before posting questions to this group AFAIK) gives me no clue.
if the answer is yes, next questions arises:
1. how to do it properly? (other than the hard way: creating those objects on app start and drop them on finished - i've not tried this myself).
2. those FB utility such as gbak backup-restore etc could it still be applicable on that DB?
3. from ethical point of view : is this intention ok ? ( considering that FB is an _open_source_ DBMS ).
if the answer is no, still i would like to thank you guys _developer_&_supporter_ for the nice product you made. ( and nice support you give on this list ).
regard,
juara purba
[Non-text portions of this message have been removed]
first of all, please forgive me if this topic has been discussed before...
i made an CS application using FB and before give it to customer, i would like my app(client side) be able to strip all the SP & Trigger source code from the database, leaving only the compiled BLR ( and customer data) .
Is is possible to do such thing? , i've searched IB6 doc especially on Data Definition Guide with no success.
Also reading and digging FB 1.5 RC8 release notes (the first commandment/rules to do before posting questions to this group AFAIK) gives me no clue.
if the answer is yes, next questions arises:
1. how to do it properly? (other than the hard way: creating those objects on app start and drop them on finished - i've not tried this myself).
2. those FB utility such as gbak backup-restore etc could it still be applicable on that DB?
3. from ethical point of view : is this intention ok ? ( considering that FB is an _open_source_ DBMS ).
if the answer is no, still i would like to thank you guys _developer_&_supporter_ for the nice product you made. ( and nice support you give on this list ).
regard,
juara purba
[Non-text portions of this message have been removed]