Subject | Cross DB question |
---|---|
Author | Daniel Jimenez |
Post date | 2004-10-26T08:18:06Z |
I have posted this question in the Firebird group, but feel that it may be
more appropriate to post this question here.
I am designing DB's for several applications where there is a lot of shared
data, FK's, etc. Since FireBird does not support cross DB references,
constraints, triggers, etc. How do people normally deal with this problem
when writing large complex systems with multiple DB's where there exist a
need to created FK's across DB's which are required within triggers,
constraints ,etc for the purpose of insertion, deletion and updates.
How do you attack the problem of transaction handling? Etc.
danieL
____________________________
Comvision Pty. Ltd.
www.comvision.net.au
more appropriate to post this question here.
I am designing DB's for several applications where there is a lot of shared
data, FK's, etc. Since FireBird does not support cross DB references,
constraints, triggers, etc. How do people normally deal with this problem
when writing large complex systems with multiple DB's where there exist a
need to created FK's across DB's which are required within triggers,
constraints ,etc for the purpose of insertion, deletion and updates.
How do you attack the problem of transaction handling? Etc.
danieL
____________________________
Comvision Pty. Ltd.
www.comvision.net.au