Re: Remove sqlite2 from trunk
| From: | Scott MacVicar | Date: | Fri, 18 Jun 2010 18:08:30 +0000 |
| Subject: | Re: Remove sqlite2 from trunk | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48833@lists.php.net to get a copy of this message | ||
On Jun 18, 2010, at 10:50 AM, Jonathan Bond-Caron wrote:
> On Wed Jun 16 07:04 AM, Ilia Alshanetsky wrote:
>>>> drop the Sqlite2 extensions from Trunk as they are superseded by
>> the
>>> Sqlite3
>>>> extensions. The sqlite2 library is no longer maintainer and the
>>>> migration path from version 2 to 3 is very simple. Unless there
>>>> any objections, I'd like to make this happen in the next week or two.
>>>
>
> I'm all for starting to use sqlite3 but I found two issues with the
> migration to the new api:
>
> a) sqlite_busy_timeout is not available in sqlite3.c
>
> This is important for an application to return a failure right away instead
> of wait for locks to be release.
> The patch looks simple since it's a wrapper for
There is a patch going around, someone should commit it or I will.
>
> SQLITE_API int sqlite3_busy_timeout(sqlite3*, int ms);
>
> b) No persistent connections
>
> Any reason why it wasn't migrated from sqlite.c?
>
Persistent connections make sense if there is an actual overhead in creating a socket etc, it
doesn't really apply and is actually more dangerous if something is left unfinished and locks
the DB.
- S