#25501 [Opn->Bgs]: The SQLite_open() truncate non SQLite Data Bases file
| From: | wez@php.net | Date: | Fri, 12 Sep 2003 00:03:52 +0000 |
| Subject: | #25501 [Opn->Bgs]: The SQLite_open() truncate non SQLite Data Bases file | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-47483@lists.php.net to get a copy of this message | ||
ID: 25501
Updated by: wez@php.net
Reported By: o_gangrel at hotmail dot com
-Status: Open
+Status: Bogus
Bug Type: SQLite related
Operating System: Windows 98
PHP Version: 5.0.0b1 (beta1)
New Comment:
Not a bug in PHP but in the sqlite library.
Please report the problem here:
http://www.sqlite.org/cvstrac/tktnew
Previous Comments:
------------------------------------------------------------------------
[2003-09-11 19:03:24] o_gangrel at hotmail dot com
Description:
------------
I am using the configuration Apache/2.0.43 (Win32) PHP/5.0.0b1 with PHP
as a module of Apache.
Using the sqlite_open() if the file exists and this file is not a
SQLite Data Base file it is opened normally, the querys always return
normally with an empty result set. But when a table is created (I guess
the other CREATE sql commands accepted by the SQLite) it truncates the
file and change the file to a SQLite Data Base file.
I found solutions to not hapen this erro, but this is not expected.
And I'm sorry, I didn't tested the CVS version and other vertion of the
Apache and SQLite module.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=25501&edit=1