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
2011/11/16 Ferenc Kovacs tyra3l@gmail.com:
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
2011/11/16 Ferenc Kovacs tyra3l@gmail.com:
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.
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
2011/11/16 Ferenc Kovacs tyra3l@gmail.com:
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.
you mean the pecl package description?
I can change it, but where should it point to? sqlite3? or simply
unmaintained?
PDOSqlite?
cheers,
Derick
2011/11/16 Ferenc Kovacs tyra3l@gmail.com:
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.
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
2011/11/16 Ferenc Kovacs tyra3l@gmail.com:
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.
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.
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
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
hi,
2011/11/16 Philip Olson philip@roshambo.org:
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
hi,
2011/11/16 Philip Olson philip@roshambo.org:
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.
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
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 philip@roshambo.org:
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
2011/11/17 Johannes Schlüter johannes@schlueters.de
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
open a bug (doc bug) and add it to the TODOs, so it won't be forgotten.
2011/11/18 Ferenc Kovacs tyra3l@gmail.com:
2011/11/17 Johannes Schlüter johannes@schlueters.de
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
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
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