From: "Dmitry Yemanov" <dimitr@...>

> "Martijn Tonies" <m.tonies@...> wrote:
> >
> > Beats me, but why exactly is it parsed? I thought gbak just "stored" the
> BLR
> > and data?
>
> GBAK is just a usual client program. When something is stored in system
> tables (by you, GBAK or the server itself), the engine validates the

changes

> on commit and adjusts the metadata cache. This causes BLR to be parsed and
> dependencies to be stored. Note that dependencies are not backed up.

Right. So gbak DOES insert directly into the system tables, it doesn't issue
CREATE TABLE statements (and the like), correct?

I would still suggest creating a special "restore" database state (in which
no
additional connections are permitted). How about backing up dependencies
and simply storing the BLR without parsing in this state?

Or would that defeat the "clean up" of a backup/restore cycle?


Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com