Hi folks --
A couple of years ago, IIRC, someone posted a notice that MivaSQL sometimes requires semicolons at the end of queries, otherwise it will generate error message. Since then, I've usually put semicolons at the end of all queries I write, to be safe for both MivaSQL and MySQL.
In the last couple of weeks, I've gotten a couple of reports of module errors, and now it seems like the problem is the exact opposite. MivaSQL is saying:
Syntax Error: Expected operator, found ';'
-- when it encounters a perfectly valid query that ends with a semicolon. In some cases, the error message is "SQL command not properly ended."
So, a few questions:
- What's the real deal on semicolons? Did something change recently?
- Is Miva starting to use MivaSQL by default when creating new stores, or upgrading old ones? I'm surprised that two of my clients have had these problems recently; both of them had been using my module for a long time. I wonder if there are going to be more of these popping up?
- Can we get an update to MivaSQL that will fix this? If so, how soon?
Thanks --
A couple of years ago, IIRC, someone posted a notice that MivaSQL sometimes requires semicolons at the end of queries, otherwise it will generate error message. Since then, I've usually put semicolons at the end of all queries I write, to be safe for both MivaSQL and MySQL.
In the last couple of weeks, I've gotten a couple of reports of module errors, and now it seems like the problem is the exact opposite. MivaSQL is saying:
Syntax Error: Expected operator, found ';'
-- when it encounters a perfectly valid query that ends with a semicolon. In some cases, the error message is "SQL command not properly ended."
So, a few questions:
- What's the real deal on semicolons? Did something change recently?
- Is Miva starting to use MivaSQL by default when creating new stores, or upgrading old ones? I'm surprised that two of my clients have had these problems recently; both of them had been using my module for a long time. I wonder if there are going to be more of these popping up?
- Can we get an update to MivaSQL that will fix this? If so, how soon?
Thanks --
Comment