phpsqliteadmin-devel

[Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Firman W. <fi...@gm...>]

Last night I read about pdo_sqlite extension, it's support SQLite3. I
wondering why the SQLite extension is very slow to upgrade the engine
into version 3. And this morning I asked to SQLite mailing-list about
SQLite3 backward compatibility, then I got SQLite3 isn't support
SQLite2 databases.

Now, the problem is, If we want phpsla support SQLite3 too, we need
use pdo_sqlite extension for it, but then when we support both of
SQLite2 and SQLite3 we use 2 extensions with very different behaviour.

My solution is create the pdo2sqlite or sqlite2pdo wrapper, so we just
only need to call the same function for same operations. What do you
think guys? And does anyone has create the sqlite2pdo or pdo2sqlite?

Other problem is, how to know a database is SQLite2 or SQLite3 format?

Regards,
--=20
Firman Wandayandi
Never Dreamt Before (http://php.hm/~firman/)

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Felipe L. <ff...@gm...>]

IMHO we should focus on SQLite2 until php5 upgrades its sqlite
extension to SQLite3 officially. In fact, I=B4m not too sure how we
should deal w/ this issue, but I imagine that php devel team have good
reasons to remain on SQLite2.

I would like to hear some words from Yves too...

Felipe Lopes

On 8/25/05, Firman Wandayandi <fi...@gm...> wrote:
> Last night I read about pdo_sqlite extension, it's support SQLite3. I
> wondering why the SQLite extension is very slow to upgrade the engine
> into version 3. And this morning I asked to SQLite mailing-list about
> SQLite3 backward compatibility, then I got SQLite3 isn't support
> SQLite2 databases.
>=20
> Now, the problem is, If we want phpsla support SQLite3 too, we need
> use pdo_sqlite extension for it, but then when we support both of
> SQLite2 and SQLite3 we use 2 extensions with very different behaviour.
>=20
> My solution is create the pdo2sqlite or sqlite2pdo wrapper, so we just
> only need to call the same function for same operations. What do you
> think guys? And does anyone has create the sqlite2pdo or pdo2sqlite?
>=20
> Other problem is, how to know a database is SQLite2 or SQLite3 format?
>=20
> Regards,
> --
> Firman Wandayandi
> Never Dreamt Before (http://php.hm/~firman/)
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Phpsqliteadmin-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
>

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Yves G. <yg...@mi...>]

On Thursday 25 August 2005 20:15, Felipe Lopes wrote:
> IMHO we should focus on SQLite2 until php5 upgrades its sqlite
> extension to SQLite3 officially. In fact, I=B4m not too sure how we
> should deal w/ this issue, but I imagine that php devel team have
> good reasons to remain on SQLite2.
>
> I would like to hear some words from Yves too...

php 5.1 will be able to use sqlite v2 (through the php-sqlite extension)=20
and v3 through the pdo_sqlite driver.

So we should also support both.

> Felipe Lopes
>
> On 8/25/05, Firman Wandayandi <fi...@gm...> wrote:
> > Last night I read about pdo_sqlite extension, it's support SQLite3.
> > I wondering why the SQLite extension is very slow to upgrade the
> > engine into version 3. And this morning I asked to SQLite
> > mailing-list about SQLite3 backward compatibility, then I got
> > SQLite3 isn't support SQLite2 databases.
> >
> > Now, the problem is, If we want phpsla support SQLite3 too, we need
> > use pdo_sqlite extension for it, but then when we support both of
> > SQLite2 and SQLite3 we use 2 extensions with very different
> > behaviour.
> >
> > My solution is create the pdo2sqlite or sqlite2pdo wrapper, so we
> > just only need to call the same function for same operations. What
> > do you think guys?

I think I like that idea

> > And does anyone has create the sqlite2pdo or=20
> > pdo2sqlite?

no...

> > Other problem is, how to know a database is SQLite2 or SQLite3
> > format?

To detect whether a file is v2 or v2 IIRC you have to open it and read=20
the first dozen of bytes, they have an id of the version of the db=20
file. This is not efficient as we would to it on each pageload...

We should add a version parameter in the alias definition, and in case=20
it's not set, we can always fall back to opening the file and read the=20
version there.

DBs that are created through phpsla will have this version parameter set=20
correctly.


regards,
Yves


p.s.
Firman:
Fatal error: Only variables can be passed by reference=20
in /home/firman/public_html/blog/nucleus/libs/BLOG.php on line 187
;-)

> > Regards,
> > --
> > Firman Wandayandi
> > Never Dreamt Before (http://php.hm/~firman/)
> >
> >
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> > Practices Agile & Plan-Driven Development * Managing Projects &
> > Teams * Testing & QA Security * Process Improvement & Measurement *
> > http://www.sqe.com/bsce5sf
> > _______________________________________________
> > Phpsqliteadmin-devel mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices Agile & Plan-Driven Development * Managing Projects & Teams
> * Testing & QA Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Phpsqliteadmin-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel

--=20
Linux 2.6.12 #1 Sat Jul 9 23:28:04 CEST 2005 i686
 20:29:18 up  1:43,  0 users,  load average: 0.07, 0.52, 0.56

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Firman W. <fi...@gm...>]

On 8/26/05, Yves Glodt <yg...@mi...> wrote:
> On Thursday 25 August 2005 20:15, Felipe Lopes wrote:
> > IMHO we should focus on SQLite2 until php5 upgrades its sqlite
> > extension to SQLite3 officially. In fact, I=B4m not too sure how we
> > should deal w/ this issue, but I imagine that php devel team have
> > good reasons to remain on SQLite2.
> >

Yeah, SQLite2 still our focus, but I see peoples started to use
SQLite3. So we need to do something for this issue, we don't want
phpsla throwed out just because they use SQLite3.

> > I would like to hear some words from Yves too...
>=20
> php 5.1 will be able to use sqlite v2 (through the php-sqlite extension)
> and v3 through the pdo_sqlite driver.
>=20
> So we should also support both.
>=20

OK, clear.

> > Felipe Lopes
> >
> > On 8/25/05, Firman Wandayandi <fi...@gm...> wrote:
> > > Last night I read about pdo_sqlite extension, it's support SQLite3.
> > > I wondering why the SQLite extension is very slow to upgrade the
> > > engine into version 3. And this morning I asked to SQLite
> > > mailing-list about SQLite3 backward compatibility, then I got
> > > SQLite3 isn't support SQLite2 databases.
> > >
> > > Now, the problem is, If we want phpsla support SQLite3 too, we need
> > > use pdo_sqlite extension for it, but then when we support both of
> > > SQLite2 and SQLite3 we use 2 extensions with very different
> > > behaviour.
> > >
> > > My solution is create the pdo2sqlite or sqlite2pdo wrapper, so we
> > > just only need to call the same function for same operations. What
> > > do you think guys?
>=20
> I think I like that idea
>=20
> > > And does anyone has create the sqlite2pdo or
> > > pdo2sqlite?
>=20
> no...
>=20

So, we need to work on that. Anyone want to create it first? Felipe? Yves?

> > > Other problem is, how to know a database is SQLite2 or SQLite3
> > > format?
>=20
> To detect whether a file is v2 or v2 IIRC you have to open it and read
> the first dozen of bytes, they have an id of the version of the db
> file. This is not efficient as we would to it on each pageload...
>=20
> We should add a version parameter in the alias definition, and in case
> it's not set, we can always fall back to opening the file and read the
> version there.
>=20
> DBs that are created through phpsla will have this version parameter set
> correctly.
>=20

Nice idea. And also we need to think about "phpsla" system db, should
we use SQLite2 or SQLite3 or both (2 databases)?

>=20
> regards,
> Yves
>=20
>=20
> p.s.
> Firman:
> Fatal error: Only variables can be passed by reference
> in /home/firman/public_html/blog/nucleus/libs/BLOG.php on line 187
> ;-)
>=20

Hah, What's that? ;-S I think this problem with PHP 5.1 at dotgeek
server. BTW, thanks for info Yves. ;-)

> > > Regards,
> > > --
> > > Firman Wandayandi
> > > Never Dreamt Before (http://php.hm/~firman/)
> > >
> > >


--=20
Firman Wandayandi
Never Dreamt Before (http://php.hm/~firman/)

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Felipe L. <ff...@gm...>]

Ok! I will read a bit about sqlite3 on php...Just to check what is new

OFF: install google talk guys!! Its awesome....and then add me ;-)

Felipe Lopes

On 8/25/05, Yves Glodt <yg...@mi...> wrote:
> On Thursday 25 August 2005 20:15, Felipe Lopes wrote:
> > IMHO we should focus on SQLite2 until php5 upgrades its sqlite
> > extension to SQLite3 officially. In fact, I=B4m not too sure how we
> > should deal w/ this issue, but I imagine that php devel team have
> > good reasons to remain on SQLite2.
> >
> > I would like to hear some words from Yves too...
>=20
> php 5.1 will be able to use sqlite v2 (through the php-sqlite extension)
> and v3 through the pdo_sqlite driver.
>=20
> So we should also support both.
>=20
> > Felipe Lopes
> >
> > On 8/25/05, Firman Wandayandi <fi...@gm...> wrote:
> > > Last night I read about pdo_sqlite extension, it's support SQLite3.
> > > I wondering why the SQLite extension is very slow to upgrade the
> > > engine into version 3. And this morning I asked to SQLite
> > > mailing-list about SQLite3 backward compatibility, then I got
> > > SQLite3 isn't support SQLite2 databases.
> > >
> > > Now, the problem is, If we want phpsla support SQLite3 too, we need
> > > use pdo_sqlite extension for it, but then when we support both of
> > > SQLite2 and SQLite3 we use 2 extensions with very different
> > > behaviour.
> > >
> > > My solution is create the pdo2sqlite or sqlite2pdo wrapper, so we
> > > just only need to call the same function for same operations. What
> > > do you think guys?
>=20
> I think I like that idea
>=20
> > > And does anyone has create the sqlite2pdo or
> > > pdo2sqlite?
>=20
> no...
>=20
> > > Other problem is, how to know a database is SQLite2 or SQLite3
> > > format?
>=20
> To detect whether a file is v2 or v2 IIRC you have to open it and read
> the first dozen of bytes, they have an id of the version of the db
> file. This is not efficient as we would to it on each pageload...
>=20
> We should add a version parameter in the alias definition, and in case
> it's not set, we can always fall back to opening the file and read the
> version there.
>=20
> DBs that are created through phpsla will have this version parameter set
> correctly.
>=20
>=20
> regards,
> Yves
>=20
>=20
> p.s.
> Firman:
> Fatal error: Only variables can be passed by reference
> in /home/firman/public_html/blog/nucleus/libs/BLOG.php on line 187
> ;-)
>=20
> > > Regards,
> > > --
> > > Firman Wandayandi
> > > Never Dreamt Before (http://php.hm/~firman/)
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> > > Practices Agile & Plan-Driven Development * Managing Projects &
> > > Teams * Testing & QA Security * Process Improvement & Measurement *
> > > http://www.sqe.com/bsce5sf
> > > _______________________________________________
> > > Phpsqliteadmin-devel mailing list
> > > Php...@li...
> > > https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
> >
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> > Practices Agile & Plan-Driven Development * Managing Projects & Teams
> > * Testing & QA Security * Process Improvement & Measurement *
> > http://www.sqe.com/bsce5sf
> > _______________________________________________
> > Phpsqliteadmin-devel mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
>=20
> --
> Linux 2.6.12 #1 Sat Jul 9 23:28:04 CEST 2005 i686
>  20:29:18 up  1:43,  0 users,  load average: 0.07, 0.52, 0.56
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Phpsqliteadmin-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
>

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Firman W. <fi...@gm...>]

On 8/26/05, Felipe Lopes <ff...@gm...> wrote:
> Ok! I will read a bit about sqlite3 on php...Just to check what is new
>=20

OK, and create the wrapper too Felipe while you read it ;-)

> OFF: install google talk guys!! Its awesome....and then add me ;-)
>=20

Sure, I will download it first.

> Felipe Lopes
>=20
> On 8/25/05, Yves Glodt <yg...@mi...> wrote:
> > On Thursday 25 August 2005 20:15, Felipe Lopes wrote:
> > > IMHO we should focus on SQLite2 until php5 upgrades its sqlite
> > > extension to SQLite3 officially. In fact, I=B4m not too sure how we
> > > should deal w/ this issue, but I imagine that php devel team have
> > > good reasons to remain on SQLite2.
> > >
> > > I would like to hear some words from Yves too...
> >
> > php 5.1 will be able to use sqlite v2 (through the php-sqlite extension=
)
> > and v3 through the pdo_sqlite driver.
> >
> > So we should also support both.
> >
> > > Felipe Lopes
> > >
> > > On 8/25/05, Firman Wandayandi <fi...@gm...> wrote:
> > > > Last night I read about pdo_sqlite extension, it's support SQLite3.
> > > > I wondering why the SQLite extension is very slow to upgrade the
> > > > engine into version 3. And this morning I asked to SQLite
> > > > mailing-list about SQLite3 backward compatibility, then I got
> > > > SQLite3 isn't support SQLite2 databases.
> > > >
> > > > Now, the problem is, If we want phpsla support SQLite3 too, we need
> > > > use pdo_sqlite extension for it, but then when we support both of
> > > > SQLite2 and SQLite3 we use 2 extensions with very different
> > > > behaviour.
> > > >
> > > > My solution is create the pdo2sqlite or sqlite2pdo wrapper, so we
> > > > just only need to call the same function for same operations. What
> > > > do you think guys?
> >
> > I think I like that idea
> >
> > > > And does anyone has create the sqlite2pdo or
> > > > pdo2sqlite?
> >
> > no...
> >
> > > > Other problem is, how to know a database is SQLite2 or SQLite3
> > > > format?
> >
> > To detect whether a file is v2 or v2 IIRC you have to open it and read
> > the first dozen of bytes, they have an id of the version of the db
> > file. This is not efficient as we would to it on each pageload...
> >
> > We should add a version parameter in the alias definition, and in case
> > it's not set, we can always fall back to opening the file and read the
> > version there.
> >
> > DBs that are created through phpsla will have this version parameter se=
t
> > correctly.
> >
> >
> > regards,
> > Yves
> >
> >
> > p.s.
> > Firman:
> > Fatal error: Only variables can be passed by reference
> > in /home/firman/public_html/blog/nucleus/libs/BLOG.php on line 187
> > ;-)
> >
> > > > Regards,
> > > > --
> > > > Firman Wandayandi
> > > > Never Dreamt Before (http://php.hm/~firman/)
> > > >

--=20
Firman Wandayandi
Never Dreamt Before (http://php.hm/~firman/)

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Yves G. <yg...@mi...>]

Firman Wandayandi wrote:
> On 8/26/05, Yves Glodt <yg...@mi...> wrote:

<snip>

> 
> Nice idea. And also we need to think about "phpsla" system db, should
> we use SQLite2 or SQLite3 or both (2 databases)?

I'd say we should stay with v2 as long as possible, because v3 will only 
work with php >= 5.1, whereas v2 will work even with php4.

>>regards,
>>Yves
>>
>>
>>p.s.
>>Firman:
>>Fatal error: Only variables can be passed by reference
>>in /home/firman/public_html/blog/nucleus/libs/BLOG.php on line 187
>>;-)
>>
> 
> 
> Hah, What's that? ;-S I think this problem with PHP 5.1 at dotgeek
> server. BTW, thanks for info Yves. ;-)
> 
> 
>>>>Regards,
>>>>--
>>>>Firman Wandayandi
>>>>Never Dreamt Before (http://php.hm/~firman/)

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Firman W. <fi...@gm...>]

On 8/26/05, Yves Glodt <yg...@mi...> wrote:
> >
> > Nice idea. And also we need to think about "phpsla" system db, should
> > we use SQLite2 or SQLite3 or both (2 databases)?
>=20
> I'd say we should stay with v2 as long as possible, because v3 will only
> work with php >=3D 5.1, whereas v2 will work even with php4.
>=20

Let me clarify, PDO work on PHP5.x (5.0.x or 5.1.x). If we stay with
v2, that's mean the user *MUST* load the sqlite extension even he/she
use PHP5.x and v3 databases only with PDO extension behind phpsla.

IMHO that isn't suitable solution.
--=20
Firman Wandayandi
Never Dreamt Before (http://php.hm/~firman/)

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Yves G. <yg...@mi...>]

On Saturday 27 August 2005 06:24, Firman Wandayandi wrote:
> On 8/26/05, Yves Glodt <yg...@mi...> wrote:
> > > Nice idea. And also we need to think about "phpsla" system db,
> > > should we use SQLite2 or SQLite3 or both (2 databases)?
> >
> > I'd say we should stay with v2 as long as possible, because v3 will
> > only work with php >= 5.1, whereas v2 will work even with php4.
>
> Let me clarify, PDO work on PHP5.x (5.0.x or 5.1.x). If we stay with
> v2, that's mean the user *MUST* load the sqlite extension even he/she
> use PHP5.x and v3 databases only with PDO extension behind phpsla.

Didn't know it would also work with 5.0 :-)

> IMHO that isn't suitable solution.

It seems pdo supports both sqlite2 and sqlite3... Look here:

http://www.sita.lu:82/phpinfo.php
"PDO drivers   sqlite2, sqlite, odbc, mysql, firebird"


All you need is to specify the correct connection string, e.g.:

$db = new PDO('sqlite2:/tmp/i-man.sqlite2');	// version 2
$db = new PDO('sqlite:/tmp/i-man.sqlite3');	// version 3


I was not aware until 5 minutes ago that pdo can support both, so that 
means we could drop the use of the php_sqlite extension in favor of the 
pdo sqlite functions and support v2 and v3 in the same code (well apart 
of sqlite sql features that differ between v2 and v3).

Of course we lock out then all the users of php4 :-(

Now, comments!

Have a nice weekend,
Yves


-- 
Linux 2.6.12 #1 Sat Jul 9 23:28:04 CEST 2005 i686
 10:36:34 up 15:45,  0 users,  load average: 0.39, 0.88, 0.85

Re: [Phpsqliteadmin-devel] SQLite2 & SQLite3 compatible

[Firman W. <fi...@gm...>]

On 8/27/05, Yves Glodt <yg...@mi...> wrote:
> On Saturday 27 August 2005 06:24, Firman Wandayandi wrote:
> > On 8/26/05, Yves Glodt <yg...@mi...> wrote:
> > > > Nice idea. And also we need to think about "phpsla" system db,
> > > > should we use SQLite2 or SQLite3 or both (2 databases)?
> > >
> > > I'd say we should stay with v2 as long as possible, because v3 will
> > > only work with php >=3D 5.1, whereas v2 will work even with php4.
> >
> > Let me clarify, PDO work on PHP5.x (5.0.x or 5.1.x). If we stay with
> > v2, that's mean the user *MUST* load the sqlite extension even he/she
> > use PHP5.x and v3 databases only with PDO extension behind phpsla.
>=20
> Didn't know it would also work with 5.0 :-)
>=20

Ah, see http://pecl.php.net/package/PDO ;-)

> > IMHO that isn't suitable solution.
>=20
> It seems pdo supports both sqlite2 and sqlite3... Look here:
>=20
> http://www.sita.lu:82/phpinfo.php
> "PDO drivers   sqlite2, sqlite, odbc, mysql, firebird"
>=20
>=20
> All you need is to specify the correct connection string, e.g.:
>=20
> $db =3D new PDO('sqlite2:/tmp/i-man.sqlite2');    // version 2
> $db =3D new PDO('sqlite:/tmp/i-man.sqlite3');     // version 3
>=20
>=20
> I was not aware until 5 minutes ago that pdo can support both, so that
> means we could drop the use of the php_sqlite extension in favor of the
> pdo sqlite functions and support v2 and v3 in the same code (well apart
> of sqlite sql features that differ between v2 and v3).
>=20

Yeah, I never read it carefully, that made this problem goes easy.

> Of course we lock out then all the users of php4 :-(
>=20

No, IMHO, we should be detect the PHP version first, if it's PHP4,
then we should switch to php_sqlite extension. But if it's PHP5 we can
use PDO.

> Now, comments!
>=20
> Have a nice weekend,
> Yves
>=20
>=20

I hope nice weekend, I must be done the extra work at my job. :-)
Have a nice weekend you too!
--=20
Firman Wandayandi
Never Dreamt Before (http://php.hm/~firman/)