Sort of related, I was thinking about adding some more thread-related
code such that if a connection wasn't explicitely specified then the
last connection SET or CONNECTed to for the current thread is used,
rather than just the "last connection".
But yeah, specifying the connection by variable (be it string or
connection ptr) would be a definite step forward. Currently you cannot
write a generic function like:
int getit(char *using_connection){ EXEC SQL BEGIN DECLARE SECTION; char *s_connection = using_connection; int s_it;
EXECSQL END DECLARE SECTION;
EXEC SQL AT :s_connection SELECT it INTO :s_it FROM some_table; return( s_it );}
which could be run concurrently by multiple threads.
L.
Shridhar Daithankar writes:> On Friday 27 February 2004 20:54, Michael Meskes wrote:> > On Fri, Feb 27, 2004 at
04:22:33PM+0530, Shridhar Daithankar wrote:> > > How about, allowing 'connection *'? If somebody puts a 'connection *'>
>> there it is used. If it is a string a name search is performed. Best of> > > both worlds.> >> > How shall anyone put
apointer to a connection struct inside the SQL> > statement?> >> > It would help me a lot if you'd be able to give some
examples.>> EXEC SQL BEGIN DECLARE SECTION;> connect *connectionPtr;> EXEC SQL END DECLARE SECTION;> > EXEC SQL
CONNECTTO db AS connectionPtr;> EXEC SQL AT connectionPtr SELECT 1;> > After all, it is matter of parsing some code and
emittingequivalent C code, > isn't it?> > Shridhar
