Thanks, Mark. This is exactly what I needed to know.
 
We know about the risks making copies this way, but this is done by another person, not by ourselves. Since there is a minimal chance of having troubles, certainly they will happen (see Murphy laws....). But dividing responsabilities, each one is responsible for their working manner.
 
As you say, I infer that the way the copies are given us is the "guilty", the causer for not having the generators updated, ok ?

--- On Thu, 5/31/12, Mark Rotteveel <mark@...> wrote:


From: Mark Rotteveel <mark@...>
Subject: Re: RES: [firebird-support] Copy of the current db not updating generators
To: firebird-support@yahoogroups.com
Date: Thursday, May 31, 2012, 4:10 PM


On Thu, 31 May 2012 04:25:02 -0700 (PDT), Tupy... nambá
<anhanguera@...> wrote:
> Ok, thanks. This is well known.
>  
> Then I ask = restoring the db will put the generators in the updated
> status ? 

I am not sure what the problem is your having. Making a backup of
production and restoring it in your dev-environment, will set everything in
the database as it was at the time the backup was created including
generators. If you mean something else, please explain what you mean.

Mark


------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Visit http://www.firebirdsql.org and click the Resources item
on the main (top) menu.  Try Knowledgebase and FAQ links !

Also search the knowledgebases at http://www.ibphoenix.com

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Yahoo! Groups Links





[Non-text portions of this message have been removed]