Subject | Re: [Firebird-Architect] Vulcan architecture and lock tables |
---|---|
Author | Jim Starkey |
Post date | 2006-12-16T16:39:09Z |
Adriano dos Santos Fernandes wrote:
database engine is working or isn't working well. For the dispatch
module to find the correct provider, each provider must try to attach
the database. If the correct provider can't attach the database because
the lock file is screwed up, you won't be able use lock print to
diagnose the problem.
Something worth considering is giving lock print the database name and
letting it use the configuration system to find the possible lock files.
> Arno Brinkman wrote:There are some problems. Presumably, when you need a lock print, your
>
>> Yes, For example fb_lock_print11 can handle engine11.
>> Or a general fb_lock_print could only look for version and redirect the arguments to the right
>> fb_lock_printXX?
>>
>>
> What about put in the providers the necessary functions of
> fb_lock_print, and fb_lock_print calls it?
>
>
>
database engine is working or isn't working well. For the dispatch
module to find the correct provider, each provider must try to attach
the database. If the correct provider can't attach the database because
the lock file is screwed up, you won't be able use lock print to
diagnose the problem.
Something worth considering is giving lock print the database name and
letting it use the configuration system to find the possible lock files.