On Sat, 15 Mar 2008 12:38:20 +0100, Thomas Mortagne wrote
> On Sat, Mar 15, 2008 at 11:57 AM, rssh <[EMAIL PROTECTED]> wrote:
> >
> >  > vmassol wrote:
> >  >>
> >  >>
> >  >> On Jan 10, 2008, at 2:31 PM, rssh wrote:
> >  >>
> >  >>>
> >  >>> Good day.
> >  >>>
> >  >>> I just download xwiki, and see, that it is not possible to set name
> >  >>> of default
> >  >>> database scheme other than 'xwiki'. (Becouse xwiki.tableName is
> >  >>> hardcoded in
> >  >>> SQL statements)
> >  >>>
> >  >>> Unfortunately. this means that it is hard to use xwiki as platform
> >  >>> for web
> >  >>> application, because usually we have situation 'one application/one
> >  >>> database
> >  >>> scheme' and want to use few applications (or few version of same
> >  >>> application)
> >  >>> simultaneously.
> >  >>>
> >  >>> Question: if I change this and wull create path for configurable
> >  >>> database
> >  >>> scheme name of main xwiki instance, would this patches be accepted
> >  >>> (?) or such
> >  >>> using is out of scope of interest for xwiki community ?
> >  >>
> >  >> We'd love that patch . However it's not an easy patch (you/we'll need
> >  >> to test it in lots of different conditions: XE, XEM, different
> >  >> databases).
> >  >>
> >  >> Thanks
> >  >> -Vincent
> >  >> _______________________________________________
> >  >> users mailing list
> >  >> [email protected]
> >  >> http://lists.xwiki.org/mailman/listinfo/users
> >  >>
> >  >>
> >  >
> >  > Any news on this? I did just run into this issue...
> >
> >  For the record the jira issue is there and not implemented yet:
> >  http://jira.xwiki.org/jira/browse/XWIKI-2006
> >
> >  -Vincent
> >
> >
> >  Need to clarify:  patch is ready and need only in testing(from xwiki side,
> >  works for me) and committing.  (As I see the main reason while it not
> >  committed  yet -- lack of time of core xwiki committers, and also they just
> >  afraid touch low-level stuff [may be with some reason])
> 
> The problem was also that this patch add hql queries and almost 
> double them in non virtual mode: for each hibernate transaction it 
> execute a query to force switch to the configured database. But as 
> it's not worst than virtual mode which do exactly the same this to 
> ensure it works on the correct wiki/database.
> 

 Yes. Also note, that you pay this price only if you use this feature.

(I thinking about better solution, and can say that this is impossible 
 without changing hibernate code.)


> >
> >  Also note, that JIRA support voting, i. e. you can vote for this issue and
> >  may be this will help xwiki developers to prioritize this issue to be
resolved
> >  in non-infinite time frame.
> >
> >
> >
> >  --
> >  Ruslan Shevchenko
> >  GradSoft. http://www.gradsoft.ua
> >
> >  _______________________________________________
> >  users mailing list
> >  [email protected]
> >  http://lists.xwiki.org/mailman/listinfo/users
> >
> 
> -- 
> Thomas Mortagne
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/users



--
Ruslan Shevchenko
GradSoft. http://www.gradsoft.ua

_______________________________________________
users mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/users

Reply via email to