Subject | Re: [Firebird-Architect] Re: [firebird-support] Re: Modified code - multi connection Meta data update |
---|---|
Author | Ann W. Harrison |
Post date | 2004-09-27T18:49:50Z |
At 06:31 AM 9/27/2004, karthick srini wrote:
other users must immediately begin to check the constraint
and return errors (or cascade, or whatever) if their
operations would violate it. This is not a problem in
superserver, because it keeps a single copy of the metadata
and can adapt to changes. In classic mode, each user has
its own copy of the metadata and must be notified. Your
change does not include a notification to other Classic
connections and will result in errors in that mode.
Regards,
Ann
> Let me know what is theBecause as soon as you commit that definition, all
>significance in getting exclusive connection for
>foreign key based index alone.
other users must immediately begin to check the constraint
and return errors (or cascade, or whatever) if their
operations would violate it. This is not a problem in
superserver, because it keeps a single copy of the metadata
and can adapt to changes. In classic mode, each user has
its own copy of the metadata and must be notified. Your
change does not include a notification to other Classic
connections and will result in errors in that mode.
Regards,
Ann