Re: How to access TEMP tables using SE 5.0x and I-NET

In article <4pkkag$70k@cssun.mathcs.emory.edu>, Billy Wheeler <billy.wheeler@pixie.co.za> wrote: >At 05:15 PM 6/10/96 GMT, Noble Systems Corporation wrote: >>We are using Informix 5.0x SE engine and I-NET and TOOLS. Our 4gl >>programs use TEMP tables that need to be accessed while in different >>databases. When we deployed I-NET to distribute the processing, we can >>no longer see the temp tables over databases that span multiple >>machines. > >>Informix support has told us that SE 5.0x should support this. >They're right. It should. It's sure news to me, but I'm mostly out of the support loop nowadays. *My* recollection of temp table behavior under the two-process database architecture (e.g. versions 5.X and previous) is that temp tables are local to the sqlexec that actually opens the databases. In other words, if you create a temp table when the current database is remote, it will not persist when the database is closed. If instead you create a temp table when the current database is local, it will persist until the program exits (or until sqlexit() is called, of course). HOWEVER: "local" temp tables are inaccessible while a remote database is the current database; they will "reappear" when the current database is a local database -- ANY local database. Example: database blah {a local database} select * from loctab into temp a database rem1@remote1 select * from rem1tab into temp rem_a select * from a {gives "table not found"}... close database {at this point, rem_a is history} database blah2 {another local database} select * from a {works!} select * from rem_a {gives "table not found"} All of this is from memory; I can't easily test it now. -- Alan Denney aland@informix.com Kia toa, e nga Mango! "I'll employ my resources to make your puny lives miserable! I'll crush your pitiful dreams and ambitions like bugs in the dust!" -- Calvin