COMMIT

COMMIT

Postby Otto » Fri Mar 20, 2009 10:44 pm

Is COMMIT from xHarbour slower than Clippers?
Thanks in advance
Otto
********************************************************************
mod harbour - Vamos a la conquista de la Web
modharbour.org
https://www.facebook.com/groups/modharbour.club
********************************************************************
User avatar
Otto
 
Posts: 6328
Joined: Fri Oct 07, 2005 7:07 pm

Re: COMMIT

Postby James Bott » Sat Mar 21, 2009 1:51 am

Otto,

I don't know the answer but I wonder why you ask? Even if xHarbour is twice as slow, with a single commit the user isn't going to notice (0.1 seconds vs 0.2 seconds).

If you are processing lots of records there is no need to do a commit after each one--that defeats the purpose of the buffer.

Regards,
James
User avatar
James Bott
 
Posts: 4840
Joined: Fri Nov 18, 2005 4:52 pm
Location: San Diego, California, USA

Re: COMMIT

Postby Rick Lipkin » Sat Mar 21, 2009 2:52 am

Otto

If you are running thru a loop of records and you do a dbCommit() each time .. you will take a tremendious performance hit.

Generally, if I am in a loop and want to do a 'hard disk' write or flush the buffer .. 'ole clipper trick' .. move the record pointer .. like goto recno() . .where recno() is the record you just updated... then after your loop .. do a dbCommit()

Hope that makes sense.

Rick Lipkin
User avatar
Rick Lipkin
 
Posts: 2665
Joined: Fri Oct 07, 2005 1:50 pm
Location: Columbia, South Carolina USA


Return to FiveWin for Harbour/xHarbour

Who is online

Users browsing this forum: Google [Bot] and 86 guests