Hello all,
I was running a legacy app on a MySQL 4.0.20 server.
The app queried the server like this "SELECT count(total) as total from
tbl_nada"
For 4.0.20 the result of this query was an integer.
Running the same query on 4.1.16 returns a much larger Integer and the
app crashes.
Problem
Hello all,
I was running a legacy app on a MySQL 4.0.20 server.
The app queried the server like this "SELECT count(total) as total from
tbl_nada"
For 4.0.20 the result of this query was an integer.
Running the same query on 4.1.16 returns a much larger Integer and the
app crashes.
Problem
René Fournier wrote:
Thanks! I will try this Monday. On a related note, does the 'temporary
table' approach (creating, locking, dropping) significantly slow down
queries? I haven't had to use them yet, and my application is somewhat
performance sensitive, so... just curious.
It's actually a *lo
2006/2/4, sol beach <[EMAIL PROTECTED]>:
> What other C# applications have you previously written?
> Do you know anything more than how to spell SQL?
> Have you ever installed and administered MYSQL?
I have been working as a professional programmer for around five
years, and have been writing ente
Hi!
All this was already mentioned in the discussion thread, but I summarize it.
To make the InnoDB inserts to run as fast as possible:
1) Tune the buffer pool size and ib_logfile size as recommended at:
http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html
2) Set:
innodb_flush_lo
Jan,
if you make the InnoDB buffer pool big enough to hold all your data, or at
least all the 'hot data', and set ib_logfiles large as recommended at
http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html, then
InnoDB performance should be quite close to MEMORY/HEAP performance for
