Subject | Re: Re[2]: [Firebird-Architect] HEAD branch and ODS changes |
---|---|
Author | Paul Schmidt |
Post date | 2003-07-31T14:02:46Z |
On Thu, 2003-07-31 at 08:19, Nickolay Samofatov wrote:
by DBAs using simple copy tools on databases. The solution of course is
to maintain a registry of databases and UIDs and if a database starts
that has a mis-matched UID with the database name in the registry, then
there are two solutions, one assign it a new UID assuming it's a copy,
or throw an error, and force the DBA to do something to reset it.
> Hello, Sean,Maybe it shouldn't, half the trouble with backups and restores is caused
>
> >> While we're in the area, has anyone given any thought to
> >> creating a UID at database creation time that could be
> >> stored on the header page and used as the root for the
> >> database lock tree? This would be a very nice
> >> (though partial) solution to the database alias problem.
>
> This doesn't solve any of the problems. Currently, Firebird
> allows you to copy database file and use this copy on the
> same machine. This databases will have the same UID.
> We have original database name in database header now
> and it is no way worse than UID.
by DBAs using simple copy tools on databases. The solution of course is
to maintain a registry of databases and UIDs and if a database starts
that has a mis-matched UID with the database name in the registry, then
there are two solutions, one assign it a new UID assuming it's a copy,
or throw an error, and force the DBA to do something to reset it.