| Subject | Re: [firebird-support] Re: What is efficient Tables that are created and dropped or Records later deleted |
|---|---|
| Author | Helen Borrie |
| Post date | 2009-03-12T09:55:28Z |
At 08:41 PM 12/03/2009, you wrote:
There is a proper way to handle your requirement (where different transactions want to access the same temporary data): create PERSISTENT tables and have your application populate them with *temporary data*. When you design that table, include a session ID field that identifies the rows belonging to a set and have your external application query on that session ID. You'll also want to think about criteria for deleting the temporary data: perhaps some flag that marks the set as 'no longer needed' once the last external app has finished with it.
./heLen
>Hi MartijnThat problem was about GTTs. GTTs are not intended for your kind of requirement.
>
>Yes I had but ran into issues, see my recent thread http://tech.groups.yahoo.com/group/firebird-support/message/100703
There is a proper way to handle your requirement (where different transactions want to access the same temporary data): create PERSISTENT tables and have your application populate them with *temporary data*. When you design that table, include a session ID field that identifies the rows belonging to a set and have your external application query on that session ID. You'll also want to think about criteria for deleting the temporary data: perhaps some flag that marks the set as 'no longer needed' once the last external app has finished with it.
./heLen