Subject Re: [Firebird-Architect] Vulcan architecture and lock tables
Author Jim Starkey
Rick Debay wrote:
>> It's the same as specifying the root directory per provider. It does
>>
> work if you get your hands dirty with the configuration. If you don't do
> it, your installation is irrecoverably damaged.
>
> Perhaps is a lock file is not specified, the file name defaults to a
> value specified by the provider. Instead of a file called <machine
> name>.lck, it would be <machine name><provider name>.lck or whatever
> convention you come up with. Deployers would be able to call the file
> <my lock name>.lck, specified in the configuration.
>
>

Something like this, perhaps:

JString lockFileName = configuration->getValue (LockFileName,
LockFileNameValue);

if (lockFileName.IsEmpty())
{
gds__prefix_lock(buffer, LOCK_FILE);
lock_file = buffer;
}
else
lock_file = lockFileName;

I did that way (two years ago) so it would work both with a proper
configuration and the pre-Vulcan Firebird conventions defined in
jrd/file_params.h.

Now, I don't want to be too preachy or anything, but did it occur to you
to look at what the code already did before making your suggestion?