Javier,
- Original Message -
From: "Javier Diaz" <[EMAIL PROTECTED]>
To: "'Heikki Tuuri'" <[EMAIL PROTECTED]>
Cc: "[EMAIL PROTECTED] (E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, September 03, 2002 12:32 PM
Subject: RE: Inno D
')");
Conn->ExecuteDirect("COMMIT");
But I don't know why is impossible to do the same using the normal
TSQLQuery. I already sent the message to the borland newsgroups.
Thanks
Javier
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: 02
Javier,
it may be that the dbExpress interface is still lagging behind MySQL
development.
If I recall right, people have complained loudly in Borland newsgroups that
dbExpress created a new connection for each SQL query it issues to MySQL.
That makes the use of transactions impossible with it.
w for the ODBC connection is working fine, but the same code using
TSQLQuery (dbExpress Component) dosen't work. Do you have any idea what can
be the reason?
Thanks
Javier
-Original Message-
From: Tod Harter [mailto:[EMAIL PROTECTED]]
Sent: 02 September 2002 15:58
To: Javier Diaz
Subjec
Stanislav,
how big is the insert and update load to your table?
One user of InnoDB says that it copes with his average
load of 800 inserts/updates per second. The computer
has 4 processors.
Since InnoDB has the non-locking consistent read,
SELECT queries do not stop inserts or updates to your t
