phpsqliteadmin-devel — phpSQLiteAdmin developer mailing list

[Phpsqliteadmin-devel] SQLite ext vs PDO ext

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

Hey guys,

It's all about sqlite ext vs pdo (http://pecl.php.net/package/PDO)
ext, I'm not sure if we should keep the SQLite
(http://pecl.php.net/package/SQLite) support, the developers of it are
focus on PDO. I thought this extension will be removed at the future,
not sure about that.

But, on the other hand if we only use PDO, that's mean the php4 user
will be dead, they need to upgraded to php5.

I dunno, but we would eliminate the time cost if we use PDO.

And, I have been made the phpsla's core under sqlite ext ;-S=20

What do you think guys?
--=20
Firman Wandayandi
Never Dreamt Before (http://php.hm/~firman/)

Re: [Phpsqliteadmin-devel] Renaming the project?

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

On 9/17/05, Felipe Lopes <ff...@gm...> wrote:
> I knew Yves would not agree...I think he is right....His arguments make
> sense...Let's move on and forget it...We should be worried about our code=
,
> not about its (already nice) name.=20
>=20

Agreed!

> Besides that, we (yves) does have some rights over the name, as he create=
d
> it from scratch..Not sure if Firman knows about it, but some time ago we =
had
> a problem w/ other project that STILL (I guess) carries the same name of
> ours. If you check our forum @ sf.net, you will see people asking about t=
he
> other project...Changing phpSQLiteAdmin name is like if we give up our
> rights.=20
>  =20

I knew that, It's Ricard's project and I knew him. But seem the
project was idled at this time, I dunno he's continue the project or
not.

> And I disagree when Yves says ppl don't mind what language is used by the
> project....(I would never run an ASP app.....I might consider run a k* ap=
p
> sometime in the future though :-P)=20
>  =20
> Anyway....Lets move on=20
>  =20
> Let's focus our time on coding, please=20
>  =20

Yep, let's move on. But, I'm has bad mood on coding right now, will do
it later :-)

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

Re: [Phpsqliteadmin-devel] Renaming the project?

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

I knew Yves would not agree...I think he is right....His arguments make=20
sense...Let's move on and forget it...We should be worried about our code,=
=20
not about its (already nice) name.
 Besides that, we (yves) does have some rights over the name, as he created=
=20
it from scratch..Not sure if Firman knows about it, but some time ago we ha=
d=20
a problem w/ other project that STILL (I guess) carries the same name of=20
ours. If you check our forum @ sf.net <http://sf.net>, you will see people=
=20
asking about the other project...Changing phpSQLiteAdmin name is like if we=
=20
give up our rights.
 And I disagree when Yves says ppl don't mind what language is used by the=
=20
project....(I would never run an ASP app.....I might consider run a k* app=
=20
sometime in the future though :-P)
 Anyway....Lets move on
 Let's focus our time on coding, please
 Felipe Fontana Lopes
 On 9/16/05, Firman Wandayandi <fi...@gm...> wrote:=20
>=20
> On 9/16/05, Yves Glodt <yg...@mi...> wrote:
> > Firman Wandayandi wrote:
> > > On 9/16/05, Felipe Lopes <ff...@gm...> wrote:
> > >
> > >>We might just cut off the "PHP"....SQLiteAdmin...Or=20
> WebSQLiteAdmin...Well
> > >>Don't know actually....
> > >>
> > >
> > >
> > > Here the possibly names:
> > > 1. SQLiteAdmin (Felipe)
> > > 2. WebSQLiteAdmin (Felipe)
> > > 3. SQLiteWorks (Me)
> > >
> > >
> > >> Yves, What you think about it? I mean, about changing your project's
> > >>name....You haven't said anything about it yet....Your word is the on=
e=20
> that
> > >>really matters here ;-)
> > >>
> > >
> > >
> > > Yeah, Felipe right. Tell us your comments Yves.
> > >
> > > Regards,
> >
> > Hi (and sorry for being late...),
> >
> > I have been quite busy at work these days and must admit I did not spen=
d
> > too much time on this yet...
> >
> > So far, honestly, I can not really share the renaming-enthusiasm... If
> > we would apply the same rule than we would apply for the "PHP" part in
> > the name, we would also have to remove sqlite from the name... no?
> >
>=20
> No, we shouldn't remove the "SQLite" part.
>=20
> > I understand that for the phpsqliteadmin user it does not matter in wha=
t
> > language it is written.
> >
> > But, on the other hand, on unix, traditionally many softwares include
> > the name (or parts of) of the tool(kit)s they have been written in
> > (qcad, gtkam, gtk-gnutella, qtparted, wxprojman, php*, g*, k*, etc...)
> >
> > Apart of that, renaming will cause work, which needs time, which whould
> > be better invested in coding... (sorry I know I am the least-good place=
d
> > to speak about...)
> >
> >
> > Comments...?
> >
> >
>=20
> Yeah, I'm right to trust you Yves. I'm even never thought about our
> cost if we renaming it and also about invested.
>=20
> Now, I'm sure! I think we shouldn't rename this project, let's goes on
> the phpSQLiteAdmin and beat the others. Everyone knew, that
> phpSQLiteAdmin's bugs aren't PHP bugs anyway :-D. But we play the old
> drama like phpMyAdmin, phpPgAdmin, phpOracleAdmin, php-nuke, phpWiki,
> phpAuction, uh I don't want to tell all of them here :P, nevermind you
> right Yves, I agreed!
>=20
> Thanks Yves.
> --
> Firman Wandayandi
> Never Dreamt Before (http://php.hm/~firman/)
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
> Download it for free - -and be entered to win a 42" plasma tv or your ver=
y
> own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Phpsqliteadmin-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
>

Re: [Phpsqliteadmin-devel] Renaming the project?

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

On 9/16/05, Yves Glodt <yg...@mi...> wrote:
> Firman Wandayandi wrote:
> > On 9/16/05, Felipe Lopes <ff...@gm...> wrote:
> >
> >>We might just cut off the "PHP"....SQLiteAdmin...Or WebSQLiteAdmin...We=
ll
> >>Don't know actually....
> >>
> >
> >
> > Here the possibly names:
> > 1. SQLiteAdmin (Felipe)
> > 2. WebSQLiteAdmin (Felipe)
> > 3. SQLiteWorks (Me)
> >
> >
> >> Yves, What you think about it? I mean, about changing your project's
> >>name....You haven't said anything about it yet....Your word is the one =
that
> >>really matters here ;-)
> >>
> >
> >
> > Yeah, Felipe right. Tell us your comments Yves.
> >
> > Regards,
>=20
> Hi (and sorry for being late...),
>=20
> I have been quite busy at work these days and must admit I did not spend
> too much time on this yet...
>=20
> So far, honestly, I can not really share the renaming-enthusiasm... If
> we would apply the same rule than we would apply for the "PHP" part in
> the name, we would also have to remove sqlite from the name... no?
>=20

No, we shouldn't remove the "SQLite" part.

> I understand that for the phpsqliteadmin user it does not matter in what
> language it is written.
>=20
> But, on the other hand, on unix, traditionally many softwares include
> the name (or parts of) of the tool(kit)s they have been written in
> (qcad, gtkam, gtk-gnutella, qtparted, wxprojman, php*, g*, k*, etc...)
>=20
> Apart of that, renaming will cause work, which needs time, which whould
> be better invested in coding... (sorry I know I am the least-good placed
> to speak about...)
>=20
>=20
> Comments...?
>=20
>=20

Yeah, I'm right to trust you Yves. I'm even never thought about our
cost if we renaming it and also about invested.

Now, I'm sure! I think we shouldn't rename this project, let's goes on
the phpSQLiteAdmin and beat the others. Everyone knew, that
phpSQLiteAdmin's bugs aren't PHP bugs anyway :-D. But we play the old
drama like phpMyAdmin, phpPgAdmin, phpOracleAdmin, php-nuke, phpWiki,
phpAuction, uh I don't want to tell all of them here :P, nevermind you
right Yves, I agreed!

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

Re: [Phpsqliteadmin-devel] Renaming the project?

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

Firman Wandayandi wrote:
> On 9/16/05, Felipe Lopes <ff...@gm...> wrote:
> 
>>We might just cut off the "PHP"....SQLiteAdmin...Or WebSQLiteAdmin...Well
>>Don't know actually....
>> 
> 
> 
> Here the possibly names:
> 1. SQLiteAdmin (Felipe)
> 2. WebSQLiteAdmin (Felipe)
> 3. SQLiteWorks (Me)
> 
> 
>> Yves, What you think about it? I mean, about changing your project's
>>name....You haven't said anything about it yet....Your word is the one that
>>really matters here ;-)
>> 
> 
> 
> Yeah, Felipe right. Tell us your comments Yves.
> 
> Regards,

Hi (and sorry for being late...),

I have been quite busy at work these days and must admit I did not spend 
too much time on this yet...

So far, honestly, I can not really share the renaming-enthusiasm... If 
we would apply the same rule than we would apply for the "PHP" part in 
the name, we would also have to remove sqlite from the name... no?

I understand that for the phpsqliteadmin user it does not matter in what 
language it is written.

But, on the other hand, on unix, traditionally many softwares include 
the name (or parts of) of the tool(kit)s they have been written in 
(qcad, gtkam, gtk-gnutella, qtparted, wxprojman, php*, g*, k*, etc...)

Apart of that, renaming will cause work, which needs time, which whould 
be better invested in coding... (sorry I know I am the least-good placed 
to speak about...)


Comments...?

Re: [Phpsqliteadmin-devel] Renaming the project?

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

On 9/16/05, Felipe Lopes <ff...@gm...> wrote:
> We might just cut off the "PHP"....SQLiteAdmin...Or WebSQLiteAdmin...Well
> Don't know actually....
> =20

Here the possibly names:
1. SQLiteAdmin (Felipe)
2. WebSQLiteAdmin (Felipe)
3. SQLiteWorks (Me)

>  Yves, What you think about it? I mean, about changing your project's
> name....You haven't said anything about it yet....Your word is the one th=
at
> really matters here ;-)
> =20

Yeah, Felipe right. Tell us your comments Yves.

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

Fwd: [Phpsqliteadmin-devel] Renaming the project?

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

---------- Forwarded message ----------
From: Felipe Lopes <ff...@gm...>
Date: Sep 16, 2005 2:42 AM
Subject: Re: [Phpsqliteadmin-devel] Renaming the project?
To: fi...@gm...

We might just cut off the "PHP"....SQLiteAdmin...Or WebSQLiteAdmin...Well=
=20
Don't know actually....

Yves, What you think about it? I mean, about changing your project's=20
name....You haven't said anything about it yet....Your word is the one that=
=20
really matters here ;-)

Best Regards

Felipe Lopes

On 9/16/05, Firman Wandayandi <fi...@gm...> wrote:
>=20
> Hi Guys!
>=20
> On 9/15/05, Felipe Lopes <ff...@gm...> wrote:
> > IMHO, we should pick a new name for our project. In our case, we have=
=20
> PHP
> > and SQLite on our name :-/=20
> >
>=20
> I've been privately emailed D. Richard Hipp as SQLite team for asking
> about permission of using "SQLite" in our project name. And he said
> it's ok.
>=20
> Here my email and replies:
> ---- snip ----=20
>=20
> From: Firman Wandayandi <fi...@gm...>
> Reply-To: fi...@gm...
> To: "D. Richard Hipp" < dr...@hw...>
> Date: Sep 16, 2005 9:25 AM
> Subject: phpSQLiteAdmin Project Naming Issues
>=20
> Hi,
>=20
> We have naming issues in our project name (phpSQLiteAdmin,
> http://phpsqliteadmin.sourceforge.net)<http://phpsqliteadmin.sourceforge.=
net%29>,=20
> as you knew this project focus
> on SQLite database administration and we use "PHP" and "SQLite" in the
> project's name. PHP group sugested that we shouldn't use "PHP" in the=20
> project's name and we agreed to renaming our project name. We will
> removing the "PHP" in it and now for "SQLite".
>=20
> Consider on what's this project for, it's more clear for peoples to
> know that the software is SQLite tool if we use "SQLite" in the=20
> project's name.
>=20
> Seems no violation with SQLite's copyright agreement.
>=20
> To make sure, so I asking you as the SQLite team, Is that ok?
>=20
> Regards,
> --
> Firman Wandayandi
> Never Dreamt Before ( http://php.hm/~firman/ <http://php.hm/%7Efirman/>)
>=20
> --------
>=20
> From: D. Richard Hipp <dr...@hw...> Mailed-By: hwaci.com<http://hwaci.c=
om>
> To: fi...@gm...
> Date: Sep 16, 2005 9:57 AM
> Subject: Re: phpSQLiteAdmin Project Naming Issues
>=20
> On Fri, 2005-09-16 at 09:25 +0700, Firman Wandayandi wrote:
>=20
> > Seems no violation with SQLite's copyright agreement.=20
> >
> > To make sure, so I asking you as the SQLite team, Is that ok?
>=20
> Yes, it is ok.
> --
> D. Richard Hipp <dr...@hw...>
>=20
> ---- snip ----
>=20
> We can pick the name contains "SQLite" in it. Still not found the=20
> right name here.
> --
> Firman Wandayandi
> Never Dreamt Before (http://php.hm/~firman/ <http://php.hm/%7Efirman/>)
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by:=20
> Tame your development challenges with Apache's Geronimo App Server.
> Download it for free - -and be entered to win a 42" plasma tv or your ver=
y
> own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Phpsqliteadmin-devel mailing list
> Php...@li...=20
> https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
>

Re: [Phpsqliteadmin-devel] Renaming the project?

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

Hi Guys!

On 9/15/05, Felipe Lopes <ff...@gm...> wrote:
> IMHO, we should pick a new name for our project. In our case, we have PHP
> and SQLite on our name :-/=20
>  =20

I've been privately emailed D. Richard Hipp as SQLite team for asking
about permission of using "SQLite" in our project name. And he said
it's ok.

Here my email and replies:
---- snip ----

From: Firman Wandayandi <fi...@gm...>=09
Reply-To: fi...@gm...
To: "D. Richard Hipp" <dr...@hw...>
Date: Sep 16, 2005 9:25 AM
Subject: phpSQLiteAdmin Project Naming Issues

Hi,

We have naming issues in our project name (phpSQLiteAdmin,
http://phpsqliteadmin.sourceforge.net), as you knew this project focus
on SQLite database administration and we use "PHP" and "SQLite" in the
project's name. PHP group sugested that we shouldn't use "PHP" in the
project's name and we agreed to renaming our project name. We will
removing the "PHP" in it and now for "SQLite".

Consider on what's this project for, it's more clear for peoples to
know that the software is SQLite tool if we use "SQLite" in the
project's name.

Seems no violation with SQLite's copyright agreement.

To make sure, so I asking you as the SQLite team, Is that ok?

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

--------

From: D. Richard Hipp <dr...@hw...>=09Mailed-By: hwaci.com
To: fi...@gm...
Date: Sep 16, 2005 9:57 AM
Subject: Re: phpSQLiteAdmin Project Naming Issues

On Fri, 2005-09-16 at 09:25 +0700, Firman Wandayandi wrote:

> Seems no violation with SQLite's copyright agreement.
>
> To make sure, so I asking you as the SQLite team, Is that ok?

Yes, it is ok.
--
D. Richard Hipp <dr...@hw...>

---- snip ----

We can pick the name contains "SQLite" in it. Still not found the
right name here.
--=20
Firman Wandayandi
Never Dreamt Before (http://php.hm/~firman/)

Re: [Phpsqliteadmin-devel] Renaming the project?

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

Hi there!!
 I've never thought about it before, but after reading the link you sent I=
=20
think we should consider changing the project's name. Could you imagine the=
=20
negative impact that those many bugs in PHP-NUKE has caused to PHP? They ar=
e=20
right.
 IMHO, we should pick a new name for our project. In our case, we have PHP=
=20
and SQLite on our name :-/
 Don't ask me what name to pick though :-)
 Felipe Lopes

 On 9/15/05, Firman Wandayandi <fi...@gm...> wrote:=20
>=20
> On 9/15/05, Yves Glodt <yg...@mi...> wrote:
> > Hi guys,
> >
> > Firman proposed that we discuss a rename of the project, the reason
> > behind is that the PHP license ( http://www.php.net/license/ , read the
> > first Q in the FAQ) encourages projects NOT to use the PHP acronym in
> > their name.
> >
> > What are your opinions?
> >
> >
> > Best regards,
> > Yves
> >
>=20
> I've already told to Yves that I'm not sure about renaming this
> project or not. But we should be found the solution of this issue
> because this is about license.
>=20
> Same question with Yves, I waiting your comments.
>=20
> Regards,
> --
> Firman Wandayandi
> Never Dreamt Before (http://php.hm/~firman/)
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
> Download it for free - -and be entered to win a 42" plasma tv or your ver=
y
> own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Phpsqliteadmin-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel
>

Re: [Phpsqliteadmin-devel] Renaming the project?

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

On 9/15/05, Yves Glodt <yg...@mi...> wrote:
> Hi guys,
>=20
> Firman proposed that we discuss a rename of the project, the reason
> behind is that the PHP license ( http://www.php.net/license/ , read the
> first Q in the FAQ) encourages projects NOT to use the PHP acronym in
> their name.
>=20
> What are your opinions?
>=20
>=20
> Best regards,
> Yves
>=20

I've already told to Yves that I'm not sure about renaming this
project or not. But we should be found the solution of this issue
because this is about license.

Same question with Yves, I waiting your comments.

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

[Phpsqliteadmin-devel] Renaming the project?

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

Hi guys,

=46irman proposed that we discuss a rename of the project, the reason=20
behind is that the PHP license ( http://www.php.net/license/ , read the=20
first Q in the FAQ) encourages projects NOT to use the PHP acronym in=20
their name.

What are your opinions?


Best regards,
Yves


=2D-=20
Linux 2.6.13 #1 Mon Aug 29 22:07:30 CEST 2005 i686
 22:57:12 up  3:31,  0 users,  load average: 0.42, 0.25, 0.25

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/)

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/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...>]

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, 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

[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

[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

[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
>

[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] a small tweak

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

On Monday 15 August 2005 21:55, Thomas Andrews wrote:
> On 8/14/05, Yves Glodt <yg...@mi...> wrote:
> > This feature exists already in the cvs version of phpsqliteadmin,
> > you can see the code here:
> >
> > http://cvs.sourceforge.net/viewcvs.py/phpsqliteadmin/phpsqliteadmin
> >/table_browse.php?rev=1.3&view=markup
>
> Hi Yves,
>
> Excellent! I got the phpsqliteadmin module from CVS - perfect.
>
> Many Thanks,

You are welcome, enjoy it!

> Thomas

-- 
Linux 2.6.12 #1 Sat Jul 9 23:28:04 CEST 2005 i686
 23:30:00 up 2 days, 20:31,  1 user,  load average: 0.63, 0.50, 0.88

Re: [Phpsqliteadmin-devel] a small tweak

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

On Saturday 13 August 2005 12:14, Thomas Andrews wrote:
> Hi,

Hello!

> I've never done any php before, so I'm having a bit of difficulty
> trying to make a tiny change to table_browse.php. All I want to do is
> have a heading on top of each table column when browsing tables. Like
> when you have ".explain ON" in sqlite. How would I do that ?

This feature exists already in the cvs version of phpsqliteadmin, you 
can see the code here:

http://cvs.sourceforge.net/viewcvs.py/phpsqliteadmin/phpsqliteadmin/table_browse.php?rev=1.3&view=markup


The part responsible for adding the headers is here:

for ($i=0; $i<$userdbh->numFields(); $i++) {
    print "<th>" . $userdbh->fieldName($i)  . "</th>\n";
}


If you plan to tinker with phpsqliteadmin, I would suggest that you 
check out the cvs version, it has had some changes since 0.2


best regards!,
Yves

> Many thanks!
> Thomas
>
>
> -------------------------------------------------------
> 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

-- 
Linux 2.6.12 #1 Sat Jul 9 23:28:04 CEST 2005 i686
 10:05:30 up 1 day,  7:07,  1 user,  load average: 1.76, 1.15, 1.23

[Phpsqliteadmin-devel] a small tweak

[Thomas A. <pa...@gm...>]

Hi,

I've never done any php before, so I'm having a bit of difficulty trying
to make a tiny change to table_browse.php. All I want to do is have a
heading on top of each table column when browsing tables. Like when you
have ".explain ON" in sqlite. How would I do that ?

Many thanks!
Thomas

Re: [Phpsqliteadmin-devel] copy a cvs module

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

On 7/27/05, Yves Glodt <yg...@mi...> wrote:
> Hi Guys,
>=20
> argh, I spend half of the sunday afternoon trying to figure out how to
> copy a cvs module, e.g. from
> CVSROOT/phpsqliteadmin to CVSROOT/phpsqliteadmin2 but I failed
> miserably... Does someone have a clue how to do that?
>=20

Sorry, I'm not an expert on CVS, I has same problem when removing a
directory, I think I need to learn more the CVS. :-)

> Firman, If not then I suggest that you can use the checkout you have on
> your disk for your ideas, and when you feel like you wanna check
> something in, you can try to check it in directly as new module....
> What do you think?
>=20

Ok, I guess so. I'm collecting the ideas first then commit it.

>
> Regards,
> Yves

--=20
Firman Wandayandi
:: Never Dreamt Before ::
http://php.hm/~firman/
firman(@)php.net | firmanw(@)gmail.com