You are correct! Forgive me people for my previous posts. They were
based on the information of an online article that I read sometime
ago. I never tested and never used the methods described. I just
trusted what I read.

Now I did some tests and the restored database keeps the
triggers/procedures working.

Living and learning... do not trust everything you read... better test
it first :)

I will contact the article's author and try to find out why he told that
the SPs/Triggers not survive a backup/restore.

A test that I cannot do is to backup a db on a Intel machine and
restore it into a non-intel-compatible machine... maybe that would
break the BLR (just a guess). Can someone test that and post the
results?

Carlos
http://www.warmboot.com.br
FireBase - http://www.FireBase.com.br

f> I use this 'trick' a lot (with stored procedures and triggers), and
f> there is no problem after a backup/restore. The triggers and
f> procedures still works after that.

f> --- In firebird-support@yahoogroups.com, "Carlos H. Cantu"
f> <listas@w...> wrote:

>> ABS> This works,
>>
>> ABS> But AFAIK the BLR code could be reverse-engineered (and I

f> think it's not

>> ABS> too dificult)
>>
>> ABS> see you !
>>
>> And remember that when you do a backup/restore all your stored
>> procedures are gone since there is no source code to recreate them!
>>
>> Carlos
>> http://www.warmboot.com.br
>> FireBase - http://www.FireBase.com.br
>>
>> ABS> Myles Wakeham wrote:
>>
>> >>>On 12-May-2004 14:49:24, Salim Naufal wrote:
>> >>>I have tried the following,
>> >>>
>> >>>Update rdb$procedures set rdb$procedure_source = ''
>> >>>
>> >>>It deleted the source text of the procedure leaving the BLR.

f> The procedure

>> >>>still works fine.
>> >>>
>> >>>Before doing that, it would be wise to have that stuff

f> validated by one of

>> >>>the list gurus.