| List: | MySQL on Win32 | « Previous MessageNext Message » | |
| From: | David Vergin | Date: | June 12 2000 6:51pm |
| Subject: | MySQL server has gone away... SOLVED | ||
| View as plain text | |||
Let's document this concisely for the archives: The error message: DBD::mysql::st execute failed: MySQL server has gone away at... was caused by a $dbh->disconnect() statement that inadvertently ended up occurring before the $sth->execute() that produced the error. Thank you Brian Smith and Sinisa Milivojevic for responses that helped point out the solution. Regards to all, david vergin
| Thread | ||
|---|---|---|
| • Data Modeling Settings | Roger Niederland | 11 Jun |
| • execute failed: MySQL server has gone away... NOT | David Vergin | 12 Jun |
| • Re: execute failed: MySQL server has gone away... NOT | Sinisa Milivojevic | 12 Jun |
| • Re: execute failed: MySQL server has gone away... NOT | Brian Smith | 12 Jun |
| • MySQL server has gone away... SOLVED | David Vergin | 12 Jun |
| • Re: Data Modeling Settings | Tonci Grgin | 27 Jun |
| • Re: Data Modeling Settings | Roger Niederland | 28 Jun |
| • RE: MySQL server has gone away... SOLVED | Nathan R. Neulinger | 12 Jun |
