Subject | Re: [Firebird-Architect] Vulcan architecture and lock tables |
---|---|
Author | Jim Starkey |
Post date | 2006-12-16T13:45:13Z |
= m. Th = wrote:
> Sorry for jumping in, but, as always not knowing your code, perhaps ISorry, a lock table is per-engine, not per-database.
> can give another way to see the things. You'll decide if is something
> useful here...
>
> Perhaps you can do a lock table for each database and embed this
> somewhere in the db file and/or in a shared memory zone (recommended,
> for speed).