wrong
on this. I can't think of any reason to force a rewrite the same data to
disk.
On Sep 20, 2004, at 3:49 PM, Jeff Demel wrote:
That's what I was afraid of.
Now I have to add a bunch of code to check the data before sending
(pull the record, compare the data, then decide to run the up
QL doesn't
waste the time to lock the table, write the data and update the indexes.
It's much more efficient this way.
On Sep 20, 2004, at 3:22 PM, Jeff Demel wrote:
I'm seeing some odd behavior when I run an UPDATE query, and need to
know if this is something that MySQL does.
I'm seeing some odd behavior when I run an UPDATE query, and need to
know if this is something that MySQL does. It could be something the
MySQLDirect .NET provider is doing, and to cover that possibility I've
sent an email to their support team.
So anyway, here's the scenario.
If I run an UPDA
I recently had an issue where I was getting "timeout waiting for
connection" and "max pool size" type errors. I finally was able to
resolve the problem by setting pooling=false in the connection string.
While I'm happy to have resolved the error, it made me realize that I
have no idea what is
