phpwiki-talk

[Phpwiki-talk] Better SQL backend for Mysql

[Manuel V. <man...@gm...>]

Hi all,

I'm about to upgrade my phpwiki installation from 1.3.10 to, at least,
1.3.11p1 or upcoming 1.3.12.

I currently using PearDb backend and I'm reaching -sometimes- speed
problems (I guess this is due to table locking).

I started to read Adodb backend sources and it appears that this one
seems to be better than PearDB, so I have a couple of question:
* is it possible to switch from a backend to another one ?
* should I use Adodb backend instead of PearDb backend ?
* how mature/stable is Adodb backend ?
* is Adodb really faster than PearDb ?

And in a more long term approach:
* Why keeping 2 backends for the same storage medium ?
* Do you plan to remove one of them ?

Thanks for your input,
Manuel

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Reini U. <ru...@x-...>]

Manuel Vacelet schrieb:
> I'm about to upgrade my phpwiki installation from 1.3.10 to, at least,
> 1.3.11p1 or upcoming 1.3.12.
> 
> I currently using PearDb backend and I'm reaching -sometimes- speed
> problems (I guess this is due to table locking).

Probably more due to caching, unless you use a real database, not just
mysql. There true transactions gain a lot.
But fastest is by far the dba backend, because of the communication
overhead with the SQL server.

> I started to read Adodb backend sources and it appears that this one
> seems to be better than PearDB, so I have a couple of question:
> * is it possible to switch from a backend to another one ?

sure.

> * should I use Adodb backend instead of PearDb backend ?

why not?

> * how mature/stable is Adodb backend ?

Stable. With 1.3.12_rc2 I see some asymetries in the transaction logs
with postgresql, but it's not critical.

> * is Adodb really faster than PearDb ?

Yes.

> And in a more long term approach:

> * Why keeping 2 backends for the same storage medium ?

We have more than two. PDO is similar, and there are some more.

> * Do you plan to remove one of them ?

No.
-- 
Reini Urban
http://phpwiki.org/
http://helsinki.at/  http://spacemovie.mur.at/

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Manuel V. <man...@gm...>]

2006/3/2, Reini Urban <ru...@x-...>:
> Manuel Vacelet schrieb:
> > I'm about to upgrade my phpwiki installation from 1.3.10 to, at least,
> > 1.3.11p1 or upcoming 1.3.12.
> >
> > I currently using PearDb backend and I'm reaching -sometimes- speed
> > problems (I guess this is due to table locking).
>
> Probably more due to caching, unless you use a real database, not just
> mysql. There true transactions gain a lot.

And what about Mysql transaction capabilities via Innodb ?

> But fastest is by far the dba backend, because of the communication
> overhead with the SQL server.

I've already noticed this in your mails, but I wish to limit as much
as possible different storage format on my server (and I already have
~120 PhpWikis that run mysql backend).

I thank you for all your helpful responses and for great software !
--Manuel

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Oliver B. <li...@gm...>]

Reini Urban wrote:

[...]

> But fastest is by far the dba backend, because of the communication
> overhead with the SQL server.

is the "user can't login anymore after storing preferences" (with 
ENABLE_USER_NEW = true) error related to dba? If so, one wouldn't use 
dba.

Oliver
-- 
Oliver Betz, Muenchen

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Stefan <son...@ba...>]

Dba support maybe faster when loading a page without plugin which uses 
searchfunctions etc.
Fulltextsearch and most cpu intensiv plugins are much, much faster with 
mysql.

Stefan

Oliver Betz schrieb:

>Reini Urban wrote:
>
>[...]
>
>  
>
>>But fastest is by far the dba backend, because of the communication
>>overhead with the SQL server.
>>    
>>
>
>is the "user can't login anymore after storing preferences" (with 
>ENABLE_USER_NEW = true) error related to dba? If so, one wouldn't use 
>dba.
>
>Oliver
>  
>

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Reini U. <ru...@x-...>]

> Oliver Betz schrieb:
>
> >Reini Urban wrote:
> >>But fastest is by far the dba backend, because of the communication
> >>overhead with the SQL server.
> >
> >is the "user can't login anymore after storing preferences" (with
> >ENABLE_USER_NEW =3D true) error related to dba? If so, one wouldn't use
> >dba.

This dba problem was found and fixed with 1.3.12
--
Reini Urban
http://phpwiki.org/
http://spacemovie.mur.at/   http://helsinki.at/

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Oliver B. <li...@gm...>]

Reini Urban wrote:

[user can't login anymore after storing preferences]

> This dba problem was found and fixed with 1.3.12

great! Thanks, Reini!

Oliver
-- 
Oliver Betz, Muenchen

[Phpwiki-talk] Preferences and sign in error,was: Better SQL backend for Mysql

[Oliver B. <li...@gm...>]

"Reini Urban" wrote:

> > >is the "user can't login anymore after storing preferences" (with
> > >ENABLE_USER_NEW = true) error related to dba? If so, one wouldn't use
> > >dba.
> 
> This dba problem was found and fixed with 1.3.12

Sorry, the error is still present. As soon as I store certain 
preferences (Edit Area, password), the error arises ("Error parsing 
script headers: Script yielded no output.").

Interesting: I can change theme and language without error.

Oliver
-- 
Oliver Betz, Muenchen

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Reini U. <ru...@x-...>]

Manuel Vacelet schrieb:
> 2006/3/2, Reini Urban <ru...@x-...>:
>> Manuel Vacelet schrieb:
>>> I'm about to upgrade my phpwiki installation from 1.3.10 to, at least,
>>> 1.3.11p1 or upcoming 1.3.12.
>>>
>>> I currently using PearDb backend and I'm reaching -sometimes- speed
>>> problems (I guess this is due to table locking).
>> Probably more due to caching, unless you use a real database, not just
>> mysql. There true transactions gain a lot.
> 
> And what about Mysql transaction capabilities via Innodb ?

Then you have to use the mysqlt driver of ADODB and maybe extend the
PearDB backend to support this. I haven't yet tested it.
PDO (php5) also fully supports transactions, so should only be used with
transaction capable database.

Generally, ADODB pulls in all available ADODB drivers automatically.
So it's great for testing new databases.
PeadDB needs for every database a special PearDB_<driver>.php file,
otherwise it will fail to load. This is the conservative and more stable
backend.
-- 
Reini Urban
http://phpwiki.org/
http://helsinki.at/  http://spacemovie.mur.at/

Re: [Phpwiki-talk] Better SQL backend for Mysql

[Manuel V. <man...@gm...>]

2006/3/4, Reini Urban <ru...@x-...>:
> Manuel Vacelet schrieb:
> > 2006/3/2, Reini Urban <ru...@x-...>:
> >> Manuel Vacelet schrieb:
> >>> I'm about to upgrade my phpwiki installation from 1.3.10 to, at least=
,
> >>> 1.3.11p1 or upcoming 1.3.12.
> >>>
> >>> I currently using PearDb backend and I'm reaching -sometimes- speed
> >>> problems (I guess this is due to table locking).
> >> Probably more due to caching, unless you use a real database, not just
> >> mysql. There true transactions gain a lot.
> >
> > And what about Mysql transaction capabilities via Innodb ?
>
> Then you have to use the mysqlt driver of ADODB and maybe extend the
> PearDB backend to support this. I haven't yet tested it.
> PDO (php5) also fully supports transactions, so should only be used with
> transaction capable database.
>
> Generally, ADODB pulls in all available ADODB drivers automatically.
> So it's great for testing new databases.
> PeadDB needs for every database a special PearDB_<driver>.php file,
> otherwise it will fail to load. This is the conservative and more stable
> backend.

Thank you for all these informations.
I will keep you inform about my tests.

--Manuel