Subject RE: [firebird-support] Re: Problem afer trigger change
Author Alan McDonald
> --- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@...>
> wrote:
> > Yes, we just had a thread today along these lines. With most PSQL
> changes,
> > clients who are already connected will continue to use "old" PSQL
> code
> > because this is seen as an important way to maintain data consistency
> per
> > user.
>
> I could understand that approach... except that I'm the only user
> connected, and "data consistency per user" (i.e me) seems to be out-
> the-window if it's using the 'old' PSQL instead of the new (because it
> doesn't work)!

just be sure about this. You may be the only person,... but you may have
more than one connection to the DB. Admin tools, apps, etc
Alan

>
> > All structural changes to databases should really be done without
> anyone
> > connected (other than the database creator/designer/owner doing the
> > changes).
> Well this is basically the case. We have a process in place (using the
> FB service api) that includes stopping and restarting the FB service if
> metadata changes fail on constraints (when caused by other users being
> connected at the same time). A bit brutal but successful (on windows...
> but not Mac or Linux with the services api being broken... at least in
> FB 1.5... :( ).