Peter Faulks writes:
On Sat, 21 Apr 2001 14:12:20 +0300 (EEST), Sinisa Milivojevic wrote:
As our manual clearly describes one connection can be used for one
query at a time, unless you use threads and mutexes.
G'day
As I said, it worked fine b4 and I got it to work again. I _assumed_
Hi!
As our manual clearly describes one connection can be used for one
query at a time, unless you use threads and mutexes.
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*|
On Sat, 21 Apr 2001 14:12:20 +0300 (EEST), Sinisa Milivojevic wrote:
As our manual clearly describes one connection can be used for one
query at a time, unless you use threads and mutexes.
G'day
As I said, it worked fine b4 and I got it to work again. I _assumed_
the reason it fell over was
G'day,
This USED to work, then all of a sudden for no apparent reason it has
suddenly decided not to:
if I change the code thus:
if(*row1[2] == 'l')
{
;
}
else if(*row1[2] == 'e')
It completes, but of course this isn't any good.
Is there something fundamentally wrong with using the same
G'day,
This USED to work, then all of a sudden for no apparent reason it has suddenly decided
not to:
if I change the code thus:
if(*row1[2] == 'l')
{
;
}
else if(*row1[2] == 'e')
etc.
the cgi programme completes, so I don't think the problem is elsewhere.
Is there something
I wrote:
This USED to work, then all of a sudden for no apparent reason it has suddenly
decided not to:
Notwithstanding it used to work, it would _appear_ that calling mysql_free_result()
willy-nilly was the cause:
mysql_query(mysql, theSql);
res1 = mysql_store_result(mysql);
if(res1)
{
