<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
AlexRa,<br>
<br>
Since you were the one who wrote the newly introduced MySqlMigrations
class, which uses the MySqlScript class, can you please explain how we
can get around the issue that Frank is talking about? It looks like the
MySqlScript class has some hardcoded timeouts. Frank says that we might
be able to specify a timeout between 0 and 1 hour, but not more. Some
DB migrations, especially assets, might take more than 1 hour.<br>
<br>
I'm really considering rolling back to using the old driver because
this one is causing too much grief and confusion at this critical time
when we want things to be stable.<br>
<br>
Any light on this new driver, especially its limitations/bugs, and how
we can overcome them, would be very much appreciated so that we can try
to continue to use it in dev code.<br>
<br>
Thanks.<br>
Crista<br>
<br>
<br>
On 6/18/2010 10:57 AM, Frank Nichols wrote:
<blockquote
cite="mid:AANLkTikw4ZsjvBfE_aPXjYAkhC0grfCfdbb0zMzJHuWt@mail.gmail.com"
type="cite">The use of the MysqlScript class is at the heart of most
of the problems I have seen with the migration of mysql databases from
0.6.9 to 0.7.0. The problem seems to be that the default command
timeout value for processing a sql statement with this class is 30
seconds, which is far to short to alter a table inserting a column when
there are hundreds of thousands of rows in that table.
<div><br>
</div>
<div>In researching this it appears that the devart version of the
new MySql.data.dll has a version of the MysqlScript which allows you to
set the command timeout programmatically, however the mysql version of
this library does not have this property available. As far as I could
see there is currently no way to set the command timeout. So, it would
appear that automatic migrations are doomed to fail in any case where
they take more than 30 seconds.</div>
<div><br>
</div>
<div>Frank<br>
<br>
<div class="gmail_quote">On Fri, Jun 18, 2010 at 7:13 AM, Michael
Cerquoni <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:nebadon2025@gmail.com">nebadon2025@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I
have to say so far this new MySQL connector has been absolutely nothing
but trouble for Frank Nichols and myself testing Migration from 0.6.9
to 0.7, All throughout the testing we have had nothing but failure
after failure from this new MySQL connector that has been introduced.
It has been nearly impossible to move forward on to 0.7 because of
this, I have no doubt that this will be a major problem for everyone
to migrate over if you have even what seems like the most minimal
amounts of data. At this time i really have to give this new
connector a -1. Can someone please explain to me why the Original
MySQL connector that seemed to work perfectly for years has now been
replaced with one that constantly times out during migrations and gives
nothing but trouble with DNS, requires us to use additional connection
string settings, and basiclly makes moving on to 0.7 impossible for
myself and others?? I must be missing something here!
<div>
<div class="h5"><br>
<br>
<div class="gmail_quote">On Fri, Jun 18, 2010 at 6:06 AM, AlexRa <span
dir="ltr"><<a moz-do-not-send="true" href="mailto:info@adeptsql.com"
target="_blank">info@adeptsql.com</a>></span> wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
AA> But I note that I has "pooling=false;" in my own string though
its<br>
AA> not been in the example ini files for a while. Anyone know what
this<br>
AA> does and if its wise to keep it in the string if I had a working<br>
AA> 0.6.9 system with it there before?<br>
<br>
Hello Ai,<br>
<br>
Can't tell you why the "pooling=false;" was there in the 1st place, but<br>
I've noticed that it did cause connection failures on a Windows box
during<br>
performance testing (thousands mySQL requests in a loop, each with<br>
connect/disconnect). The error didn't happen without the
"pooling=false;"<br>
option. I don't know if that affects mySQL on Linux as well.<br>
<br>
Best regards,<br>
<br>
Alex<br>
<div>
<div><br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a moz-do-not-send="true"
href="https://lists.berlios.de/mailman/listinfo/opensim-dev"
target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
</div>
</div>
<font color="#888888">-- <br>
Michael Emory Cerquoni - Nebadon Izumi @ <a moz-do-not-send="true"
href="http://osgrid.org" target="_blank">http://osgrid.org</a><br>
</font><br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a moz-do-not-send="true" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a moz-do-not-send="true"
href="https://lists.berlios.de/mailman/listinfo/opensim-dev"
target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>