On Fri, 9 Jul 2004, Wez Furlong wrote:
> Stas already came up with a solution for the non-oo api; it probably
> just needs porting to the oo interface.
It already is it seams, the execQuery() method. Though I still don't
like the way how things are working :)
regards,
Derick
--
PHP Internals -
Stas already came up with a solution for the non-oo api; it probably
just needs porting to the oo interface.
--Wez.
On Fri, 9 Jul 2004 09:06:30 +0200 (CEST), Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Thu, 8 Jul 2004, Derick Rethans wrote:
>
> > After some investigation I found that if I rem
On Thu, 8 Jul 2004, Derick Rethans wrote:
> After some investigation I found that if I removed the "$ret = " before
> the query() call, then all queries are run just fine, and throw also a
> warning when I put back in the typoes.
I did some more investigations and it seems that as soon you try to
Consider this piece of code:
query($create_query);
if ($db->lastError() != SQLITE_OK) {
echo $db->lastError();
}
?>
As you can see there are two typoes (REATE instead of CREATE) so
obviously I expected to get a result value other than SQLITE_OK back,
but that didn't happen, and no
