NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
ferreira (5993)
ferreira
(email not shown publicly)
http://www.ferreira.triang.net/
Just another Brazilian Perl hacker.
(email not shown publicly)
http://www.ferreira.triang.net/
Just another Brazilian Perl hacker.
Friday October 21, 2005
05:49 PM
Bad SQL x bad RDBMS behavior
Well, as in any programming language, one occasionally makes some (or many) errors. And then the parser/compiler tells you missed the point and preferrably what you made wrong. SQL databases are among the worst language interpreters with their error messages. The longer your SQL the harder to get where is that damned error. I fed
SELECT 'a
to DBD::SQLite by mistake, only to discover that it doesn't emit an error. It passes and the answer is a result set with one row with 'aa'. This is not a DBD::SQLite issue, it is a SQLite issue that survives until the current version 3.2.7. Well, I submitted a patch to them and, in the next release, I will be surprised with "unterminated string" which is understandable (or not).
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
SQLite doesn't choke anymore on unclosed strings (Score:1)
Now it is for real (Score:1)
If you try DBD-SQLite-1.13 (with SQLite 3.3.5 sources), you will see that the issue with unterminated strings is over. You will get an error message like this:
But it never was a fault of DBD::SQLite [cpan.org] but a problem of SQLite [sqlite.org]. I am not sure if the first correction by drh missed something or if the fix only got to the sources much later. But the point is that it is just right now.