yeah yeah...I am a MORON...I know....BUT actually its got a positive side, beacuse my code that handles timeouts is working :-) So thats something.
Jeremy -----Original Message----- From: "David Brennan" <[EMAIL PROTECTED]> To: "NZ Borland Developers Group - Delphi List" <[EMAIL PROTECTED]> Date: Fri, 2 Apr 2004 09:54:08 +1200 Subject: RE: [DUG] ADO Weired ness > Jeremy... > > How do I put this? > > Everytime around you add more SQL to the query right? So the second > time > your SQL is: > > UPDATE TESTTABLE SET TEST = TEST+1 > UPDATE TESTTABLE SET TEST = TEST+1 > > The third time the SQL you are running is: > > UPDATE TESTTABLE SET TEST = TEST+1 > UPDATE TESTTABLE SET TEST = TEST+1 > UPDATE TESTTABLE SET TEST = TEST+1 > > Etc. > > See a problem here? > > David. > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of vss > > Sent: Friday, 2 April 2004 9:35 AM > > To: [EMAIL PROTECTED] > > Subject: [DUG] ADO Weired ness > > > > > > Hi All. > > We have been tracking down a problem that had occured off and on with > an > > app. we have written that used ADO. > > Basically it was comming up with Times outs, and I FINALLY tracked it > > down to the ADOQuery CommandTimeout which is because of an internal > issue. > > Anyway, we fixed the internal issue (hardware), but I have left a wee > app > > running all yeasterday and overnight, and then today when I got to > work, > > its had gone from like milliseconds to do the insert, to 20 seconds ! > > Its seems to just increase over time. > > All I am doing is :- > > > > ADOQuery1.close; > > ADOQuery1.sql.add('UPDATE TESTTABLE SET TEST = TEST+1'); > > ADOQuery1.ExecSQL; > > > > And thats it. Oh this gets triggered on a timer that fires after 10 > > seconds. > > > > This seems really strange if not BAD behaviour of the control. > > > > Anyone seen this before? or have any suggestions. > > I am going to try actually creating the query object each time it > needs > > to use it and then free it when its finished, but this seems a bit > over > > the top. > > I think its the problem with out app. and why I have never been able > to > > reporduce it. I.e. the client doesnt close the app. down, because > they > > operate 24/7 and then they say its slow, and they get the time out > error. > > > > Jeremy > > > > _______________________________________________ > > Delphi mailing list > > [EMAIL PROTECTED] > > http://ns3.123.co.nz/mailman/listinfo/delphi > > > > _______________________________________________ > Delphi mailing list > [EMAIL PROTECTED] > http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
