Subject | Re: [Firebird-Architect] Vulcan architecture and lock tables |
---|---|
Author | Dmitry Yemanov |
Post date | 2006-12-15T20:47:56Z |
Jim Starkey wrote:
work if you get your hands dirty with the configuration. If you don't do
it, your installation is irrecoverably damaged. And if you just put an
older provider into your setup (or if you upgrade your previous setup in
place), then you're in big trouble.
I have no problems with this feature for developers and/or experienced
field testers, but I would not suggest it for end users. Ever.
Dmitry
>It's the same as specifying the root directory per provider. It does
> If I remember correctly, the name of the lock file can be specified in
> the configuration for each engine provider, which should handle the
> problem quite nicely.
work if you get your hands dirty with the configuration. If you don't do
it, your installation is irrecoverably damaged. And if you just put an
older provider into your setup (or if you upgrade your previous setup in
place), then you're in big trouble.
I have no problems with this feature for developers and/or experienced
field testers, but I would not suggest it for end users. Ever.
Dmitry