sorry, utf8 should be code point or utf16 character (two surrogates if
needed). I thought I removed all references to utf8 before I sent it.
Must have overlooked it.
I was just trying to say that by character I mean the abstract character
unit that Unicode defines, not character as user perceives
I'd like to maintain a Russian version of the PHP documentation.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 9/2/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Rasmus, Wez - Any idea about timing for PDO? Are all these bugs
> crucial to fix for 5.1?
Yeah. I don't anticipate each bug as taking a long time to fix, it's
just finding the time to do it. Although we have a long weekend this
weekend, we hav
Hi,
I've made a simple patch to allow a user to retrieve the SQL syntax error
occured in either sqlite_exec(), sqlite_query() or
sqlite_unbuffered_query().
Untill now this wasn't possible, because sqlite_last_error() doesn't handle
SQL syntax errors. The patch adds an additional parameter to t
I've just tried to replicate the problem and it appears to work fine:
$db = sqlite_open(":memory:");
sqlite_exec($db, "SELECT ***");
var_dump(sqlite_error_string(sqlite_last_error($db)));
prints "SQL logic error or missing database"
Ilia
Nuno Lopes wrote:
> Hi,
>
> I've made a simple patch to
OK, I probably didn't explain the problem well. So let me separate the
problems:
the bug:
prints:
Notice: Undefined variable: errstr in /cvs/php-src/sqlite.php on line 2
Notice: Undefined variable: errstr in /cvs/php-src/sqlite.php on line 3
-
the "feature request":
prints "SQL logic
> the "feature request":
>
> $db = sqlite_open(":memory:");
> sqlite_exec($db, "SELECT column");
> var_dump(sqlite_error_string(sqlite_last_error($db)));
> ?>
>
> prints "SQL logic error or missing database", but you don't have a clue
> of what error is.
> with my patch, you can retrieve the err
On Fri, 2 Sep 2005, Ilia Alshanetsky wrote:
the "feature request":
prints "SQL logic error or missing database", but you don't have a clue
of what error is.
with my patch, you can retrieve the error (in the additional variable)
you get in the Warning message ("no such column: column").
Aha,
