Spanning transactions across machines

Path: emory!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!qt.cs.utexas.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!wvus!cbruce From: cbruce@wvus.org (Corinne Bruce) Newsgroups: comp.databases,comp.databases.informix Message-ID: <1991Nov26.174644.597@wvus.org> Date: 26 Nov 91 17:46:44 GMT Sender: cbruce@wvus.org (Corinne Bruce) Organization: World Vision U.S. I have YET another question... When our conversion (from IBM to Unix/Informix 4GL) is complete, our "database" will actually consist of several databases, spanning 4 machines and as many On-Line engines. Organizationally, the application is extremely interdepend- ent, and will need to use bits and pieces of many tables which may span On-Line engines. Problem: We can see a scenario looming which will make it necessary to process a particular "entity" as a single transaction (within Infomix BEGIN WORK and COMMIT WORK), even though it could potentially span machines/engines. My understanding is that currently this is not possible, but maybe someone out there knows better. It would make life EXTREMELY difficult if we had to break these inserts/updates into component parts and process them as individ- ual transactions, so any advice would be most welcome. Thank you! ------------------------------------------------------------ Corinne Bruce Project Lead World Vision U.S. cbruce@wvus.org 919 W. Huntington Dr. Voice: 818.357.1111 ext 3510 Monrovia, CA 91016 FAX: 818.303.6212 "Clearly you've mistaken me for someone who cares..." ------------------------------------------------------------