31 Oct
2007
31 Oct
'07
9:34 a.m.
Since I was probably not clear let me try to rephrase what I meant:
1) If what you to manipulate is data generated by xwiki (i.e.
everything in the XWiki database) then you should use the API provided
by xwiki and not manipulate this data directly.
2) If what you want to manipulate is your own data (for example data
coming from other systems) then you have to use direct JDBC connection
for sure.
This is why I asked for Harikrishan's use case as he seems to be in
use case 1 since he mentioned something about saving some text field
in the database. Typically, the standard way for doing this in XWiki
is to create an Object and let XWiki save that Object to the database.
Hope it makes sense,
-Vincent
On Oct 31, 2007, at 9:21 AM, Your XEN ICT Team - Ricardo Rodriguez
wrote:
Vincent Massol wrote:
You're the first one I see to have this need
so I'm curious to
understand what's your use case first. My belief is that you're not
using XWiki properly.
Me again jumping in others' threads! :-(
Before XWiki arrives to our lives, their are much easier now, we use
Oracle and MySQL RDBMS to store experimental data. Personal data are
stored in a LDAP enabled directory service.
To be able to read/write to/from these repositories from XWiki has
been always an objective, but always delayed as we need have more
urgent issues to solve!
Harikrishnan's entry put the issue top in our to-do list!
Let's see if this make sense for you:
We use XWiki to create a collaboration environment: the whole team
can contribute to a new document. XWiki user's database is
synchronized with our eDirectory directory service by using LDAP.
New documents include "structured" text (heading1, heading2, body,
list,...), pictures and code.
Among "code" we include small "programs" generating graphs and
tables from the relational data sharing MySQL with XWiki as RDBMS.
We use R to generate graphs and tables: to be able to call R
directly from XWiki will be a great plus, but it is not strictly
required at the current stage of development.
Documents will be eventually included as "code" as far as we would
like to use LaTeX as typesetting tool.
With this work flow (I think it is a "correct" use for XWiki), the
first thing to solve is what Harikrishnan is asking for... and ready
to contribute with!!!
So, these are only my two cents. I do hope it makes sense and helps
to clarify the problem, doesn't it?
Cheers,
--
Ricardo Rodríguez
Your XEN ICT Team
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users