Subject Re: RES: [firebird-support] Copy of the current db not updating generators
Author Hannes Streicher
Hello Tupy... nambá,

what is the setting of forced writes
because generators are outside of transaction control and thf shud be updated

> 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@...>

>> 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

Mit freundlichen Grüssen
Hannes Streicher mailto:HStreicher@...