Backup and restore doesn't "reset" the generators back to 0 or 1 or
anything.
They are as they were when the database was backed up.
We (or the sites) do backup and restores often, and it's simply not a
problem for the generators.



We've been using IB/FB for years, and have never had a generator related
(PK, etc) problem at a site, except when one of our site techs thought that
he could "fix" something his self, and went into the database "by hand" and
dinked with some stuff.

We use generators for PK's in master/detail tables with no problem
As I mentioned, for most tables, we normally use stored procedures for
inserts (called by the client applications).
ALL of out stored procedures always return at least one parameter, whichs is
a status of sorts.
The "insert" SP's that are called and the client will require the PK to work
with some other tables, return the PK along with the status parameter.
It works simple.
It works well.
We use it at some huge national sites, and have never had a problem with
PK's/generators, anything.



Best regards,
Fred Wilson
SE, Böwe Bell & Howell
fred.wilson@... <mailto:fred.wilson@...>


-----Original Message-----
From: Doug Chamberlin [mailto:yahoogroups@...]
Sent: Tuesday, November 11, 2003 12:20 PM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] Maintaining proper generator values
<SNIP>
And if you backup and restore the database without restoring the generator
values how will you reset them? That is the situation which prompted me to
implement my process of having the application check the current values
each time they run.






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