From: Rhino Date: December 17 2012 9:24pm Subject: Fwd: Re: Basic Question List-Archive: http://lists.mysql.com/mysql/228826 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit -------- Original Message -------- Subject: Re: Basic Question Date: Mon, 17 Dec 2012 15:39:39 -0500 From: Rhino To: Reindl Harald On 2012-12-17 14:34, Reindl Harald wrote: > > Am 17.12.2012 19:09, schrieb Rhino: >> Is the version of SQL statements that I write for MySQL based on the >> server version or the client version? > clearly for the server > mysql is a database-SERVER I know that. I thought that if the client is at a lower level, as in this case, I would need to write SQL that satisfies the client. In other words, features that emerged after 4.1 would have to be omitted since the client wouldn't know how to handle them. But I'm not clear what the MySQL Client even is let alone what it does so I'm prepared to accept the good news that I can write SQL at the 5.1 level and not have it be a problem for the client. > >> According to phpMyAdmin, the version of the MySQL Client is 4.1.22 but the MySQL Server version is 5.1.65. When I >> write SQL, do I need to ensure that it follows the rules as laid out in the Version 4.1 manual or the version >> Version 5.1 manual? > 5.1 > > but a server using 5.1.x with 4.1.x client libraries is misconfigured > these days and with PHP >= 5.3x mysqlnd should be sued > I can try sending a note to that effect to the hosting company but I have my doubts about whether they will care. Still, this may explain why the script generated by the Export of my table failed to work when I tried to use it to reimport my table. The second (non-comment) line it had generated was: SET time_zone = '+00:00"; As you can see, the string begins with an apostrophe but ends with quotation marks, causing a mismatch. Or maybe that's just a completely different error that has nothing to do with the client/server levels. -- Rhino