Re: [Phpwiki-talk] Multiple instances - One DB

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

Reini Urban wrote:
> Well, my way for gforge intergration would use a project-specific 
> DATABASE_PREFIX, set by the plugin.
> 
> DB: phpwiki
>   tables: project1_page, project1_version, project1_recent, ...
>           project2_page, project2_version, project2_recent, ...
> needs project_name
> you can even use different wiki engines per project.
My first version of the plugin was based on this schema.
But It wasn't accepted by gforge team leader.

> Your id scheme is simplier on the database level.
> DB: phpwiki
>   tables: page (with group_id), version, recent, ...
> needs group_id
> just one engine and one database schema.
> 
> Pro:  * You only have to do structure updates once,
>         and use a new primary index: pagename+id
>       * easier to upgrade to a new phpwiki schema and version.
> Cons: * Seperation into different wiki's is hard.
>       * you cannot do project specific phpwiki updates.
>       * will not by supported by phpwiki OOTB.
>         So gforge sites must patch the WikiDB backends.
> 
> I cannot accept your page.group_id patch into phpwiki.
> It is way to abusive.

There are no problems for me, I can maintain my patch myself: I made it, 
I assume it ;)

> The sql schema will not change anymore for sure.
> Maybe some minor issues with exotic backends have to fixed.

Great, no maintainance operations!

> Major goals are only the request enhancements in main and Request
> (GET => POST for ModeratedPage, maybe edit), check remaining request 
> problems (session, edit + redirect)
> wikiparser fixes for php5 (or output?),
> some remaining theme updates
> configurator for lists

Well, we are close to PhpWiki 1.3.11 that's a good news.

-- 
# VACELET Manuel     manuel.vacelet-abecedaire(at)st(dot)com #
# Tel:  042 6089                          +33 (0)476 92 6089 #
# STMicroelectronics                                         #
# 850, rue Jean Monet - 38926 CROLLES CEDEX - FRANCE         #