# pecl sqlite - Thread: https://externals.io/message/56340 - Original archive: https://news-web.php.net/php.internals/56340 - Started by Ferenc Kovacs on 2011-11-16T11:06:05+00:00 - Messages: 13 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #56340 — Ferenc Kovacs — 2011-11-16T11:06:05+00:00 URL: https://externals.io/message/56340#56340 Hi. We moved the sqlite ext from core to pecl with 5.4, but the http://pecl.php.net/package/sqlite still advertises using ext/sqlite instead. Is that intentional? The problem is, that for 5.3, the prefered way to use the sqlite ext is to use the one bundled in core, however for 5.4 and trunk, you can only install it from pecl. Maybe we could supersed it with ext/sqlite3? As it is in the core since 5.3, so all supported branches has it.. -- Ferenc Kovács @Tyr43l - http://tyrael.hu --- ## #56343 — Felipe Pena — 2011-11-16T11:53:16+00:00 URL: https://externals.io/message/56340#56343 · In reply to: #56340 2011/11/16 Ferenc Kovacs : > Hi. > > We moved the sqlite ext from core to pecl with 5.4, but the > http://pecl.php.net/package/sqlite still advertises using ext/sqlite > instead. > Is that intentional? > The problem is, that for 5.3, the prefered way to use the sqlite ext is to > use the one bundled in core, however for 5.4 and trunk, you can only > install it from pecl. > Maybe we could supersed it with ext/sqlite3? As it is in the core since > 5.3, so all supported branches has it.. It's not intentional, the text weren't updated. -- Regards, Felipe Pena --- ## #56345 — Ferenc Kovacs — 2011-11-16T12:35:48+00:00 URL: https://externals.io/message/56340#56345 · In reply to: #56343 > 2011/11/16 Ferenc Kovacs : > > […] > to > > […] > > It's not intentional, the text weren't updated. you mean the pecl package description? I can change it, but where should it point to? sqlite3? or simply unmaintained? -- Ferenc Kovács @Tyr43l - http://tyrael.hu --- ## #56346 — Derick Rethans — 2011-11-16T13:00:47+00:00 URL: https://externals.io/message/56340#56346 · In reply to: #56345 > > > > […] > > > you mean the pecl package description? > I can change it, but where should it point to? sqlite3? or simply > unmaintained? PDOSqlite? cheers, Derick --- ## #56347 — johannes@schlueters.de — 2011-11-16T13:34:34+00:00 URL: https://externals.io/message/56340#56347 · In reply to: #56345 > > > > […] 5.4 is not yet released so PHP core is still the primary source for that extension ;-) > you mean the pecl package description? > I can change it, but where should it point to? sqlite3? or simply > unmaintained? I would go for unmaintained. SQLite2 isn't maintained upstream for a few years. People can get the code if they have need to migrate or such, but other than that ... there's no good and simple migration path to something else. SQLite3 uses different APIs, different storage format and has a slightly different SQL standard interpretation. johannes --- ## #56348 — Philip Olson — 2011-11-16T14:00:09+00:00 URL: https://externals.io/message/56340#56348 · In reply to: #56347 > > > […] > > 5.4 is not yet released so PHP core is still the primary source for that > extension ;-) > > > […] > > I would go for unmaintained. SQLite2 isn't maintained upstream for a few > years. People can get the code if they have need to migrate or such, but > other than that ... there's no good and simple migration path to > something else. SQLite3 uses different APIs, different storage format > and has a slightly different SQL standard interpretation. We need to make pecl/sqlite work with 5.4, as currently it does not. I forget the details (and the related patch) but did work on one with Johannes many months ago. The last step (which failed) was to get pdo_sqlite2 to work with the shared PECL variant, IIRC. Then, make a release. Moving something to PECL should require that the PECL extension work with the distribution that it was [re]moved from. Otherwise, it was not moved. Johannes probably assumed I adjusted/committed the patch, and made a pecl/sqlite release, but he forgot that I forgot to do this, and I have since lost said patch and progress and most memories. Sorry :] Regards, Philip --- ## #56349 — johannes@schlueters.de — 2011-11-16T19:26:41+00:00 URL: https://externals.io/message/56340#56349 · In reply to: #56348 > We need to make pecl/sqlite work with 5.4, as currently it does not. I > forget the details (and the related patch) but did work on one with > Johannes many months ago. The last step (which failed) was to get > pdo_sqlite2 to work with the shared PECL variant, IIRC. Then, make a > release. > > Moving something to PECL should require that the PECL extension work with > the distribution that it was [re]moved from. Otherwise, it was not moved. > > Johannes probably assumed I adjusted/committed the patch, and made a > pecl/sqlite release, but he forgot that I forgot to do this, and I have > since lost said patch and progress and most memories. Sorry :] Looking at the patch from that time: The thing which was to be fixed was enabling the sqlite2 PDO driver. For that the patch added an configure option. What we discussed, but not decide, was whether we'd force the PDO driver on the user or not. If we force it on the user the user also needs to have PDO loaded, even when not using the PDO API. johannes --- ## #56365 — Pierre Joye — 2011-11-17T13:08:58+00:00 URL: https://externals.io/message/56340#56365 · In reply to: #56348 hi, 2011/11/16 Philip Olson : > We need to make pecl/sqlite work with 5.4, as currently it does not. Why? We moved it out because it is not maintained anymore. As I agree that the concept of "move to pecl" for dead extensions is a bad idea, inciting users to continue to use with 5.4 instead of migrate their code to sqlite3 is not a good thing. > I forget the details (and the related patch) but did work on one with > Johannes many months ago. The last step (which failed) was to get > pdo_sqlite2 to work with the shared PECL variant, IIRC. Then, make a > release. It can be applied to svn. I suppose we should add a note as well in the documentation about this move. > Moving something to PECL should require that the PECL extension work with > the distribution that it was [re]moved from. Otherwise, it was not moved. I disagree, it should work with the distro where it was still present. If we stop to support something with a given release, there is no point to give the wrong message to our users. However, if someone feels like it is worth maintaining this dead library binding and keep alive for 5.4+, he can indeed go ahead, but unless we have such a person, I don't think we should release it or do anything else for this extension and 5.4. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #56366 — Ferenc Kovacs — 2011-11-17T13:23:38+00:00 URL: https://externals.io/message/56340#56366 · In reply to: #56365 > hi, > > 2011/11/16 Philip Olson : > > > […] > > Why? We moved it out because it is not maintained anymore. As I agree > that the concept of "move to pecl" for dead extensions is a bad idea, > inciting users to continue to use with 5.4 instead of migrate their > code to sqlite3 is not a good thing. > > > […] > > It can be applied to svn. I suppose we should add a note as well in > the documentation about this move. > > > […] > > I disagree, it should work with the distro where it was still present. > If we stop to support something with a given release, there is no > point to give the wrong message to our users. > > However, if someone feels like it is worth maintaining this dead > library binding and keep alive for 5.4+, he can indeed go ahead, but > unless we have such a person, I don't think we should release it or do > anything else for this extension and 5.4. I think that you are both right. Either we shouldn't call it "moving it into pecl"(but dropping support or something) or it should work with that version which introduced the move. -- Ferenc Kovács @Tyr43l - http://tyrael.hu --- ## #56370 — johannes@schlueters.de — 2011-11-17T20:59:58+00:00 URL: https://externals.io/message/56340#56370 · In reply to: #56365 Just to make one thing clear: To the best of my knowledge the module works with 5.4 and trunk (it's three months since I tested, but I'm not aware of a recent big API break) only defect is that the PDO sqlite2 driver won't be there and can't be enabled in an easy way. The patch I sent yesterday fixes that in one way. The mail mentioned another way. Whoever wants to release the extension can go for it easily. Aside from this specific case it is worth to discuss the role of PECL and Siberia for the future. This should happen in a dedicated thread with some proposal for a strategy and goal. johannes > hi, > > 2011/11/16 Philip Olson : > > > […] > > Why? We moved it out because it is not maintained anymore. As I agree > that the concept of "move to pecl" for dead extensions is a bad idea, > inciting users to continue to use with 5.4 instead of migrate their > code to sqlite3 is not a good thing. > > > […] > > It can be applied to svn. I suppose we should add a note as well in > the documentation about this move. > > > […] > > I disagree, it should work with the distro where it was still present. > If we stop to support something with a given release, there is no > point to give the wrong message to our users. > > However, if someone feels like it is worth maintaining this dead > library binding and keep alive for 5.4+, he can indeed go ahead, but > unless we have such a person, I don't think we should release it or do > anything else for this extension and 5.4. > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #56416 — Ferenc Kovacs — 2011-11-18T21:23:33+00:00 URL: https://externals.io/message/56340#56416 · In reply to: #56370 2011/11/17 Johannes Schlüter > Just to make one thing clear: To the best of my knowledge the module > works with 5.4 and trunk (it's three months since I tested, but I'm not > aware of a recent big API break) only defect is that the PDO sqlite2 > driver won't be there and can't be enabled in an easy way. The patch I > sent yesterday fixes that in one way. The mail mentioned another way. > Whoever wants to release the extension can go for it easily. > > Aside from this specific case it is worth to discuss the role of PECL > and Siberia for the future. This should happen in a dedicated thread > with some proposal for a strategy and goal. > > johannes just a note: we have to update http://www.php.net/manual/en/sqlite.installation.php before 5.4 stable. -- Ferenc Kovács @Tyr43l - http://tyrael.hu --- ## #56423 — Pierre Joye — 2011-11-19T09:14:24+00:00 URL: https://externals.io/message/56340#56423 · In reply to: #56416 open a bug (doc bug) and add it to the TODOs, so it won't be forgotten. 2011/11/18 Ferenc Kovacs : > > > 2011/11/17 Johannes Schlüter > > […] > > just a note: we have to > update http://www.php.net/manual/en/sqlite.installation.php before 5.4 > stable. > -- > Ferenc Kovács > @Tyr43l - http://tyrael.hu > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #56427 — Ferenc Kovacs — 2011-11-19T12:15:05+00:00 URL: https://externals.io/message/56340#56427 · In reply to: #56423 > open a bug (doc bug) and add it to the TODOs, so it won't be forgotten. > > done: https://bugs.php.net/bug.php?id=60336 https://wiki.php.net/todo/php54 -- Ferenc Kovács @Tyr43l - http://tyrael.hu