|
|
| Author |
Message |
gupta vishal
New User
Joined: 25 Sep 2007 Posts: 14 Location: Gurgaon
|
|
|
|
Hi,
Is the hardcoding of TSQ name causes any type of problem?? Also suggest me certain ways to generate the name dynamically.
How can I delete my previously created TSQ (as the names are going to be dynamic) by previous transactions.(My shopowner is unhappy with this )
Regards,
Vishal K gupta |
|
| Back to top |
|
 |
References
|
Posted: Wed Mar 26, 2008 3:12 pm Post subject: Re: Hardcoding TSQ name |
 |
|
|
 |
enrico-sorichetti
Global Moderator
Joined: 14 Mar 2007 Posts: 2443 Location: italy
|
|
|
|
it will certainly cause problems,
if You are storing in a TS queue transaction related data, using a single identifier will certainly mix up data from different/concurrent execution of the same transaction from different terminals..
the most usual approach would be to use for a temporary TSQ a token composed for example by term_id ( 4 chars ) and tran_id ( 4 chars )
idf the data is transaction specific
if the TS data is ascratch pad to be used by more than one transaction just use the terminal id
anyway when not needed any more, all the TS queues should be purged
what do You value more...
the happiness of the shop owner, or the happiness of Your application  |
|
| Back to top |
|
 |
|
|