16 May
2011
16 May
'11
8:53 p.m.
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
16 May
16 May
8:56 p.m.
Le 16/05/11 20:53, Sergiu Dumitriu a écrit :
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
+1
I've no knowledge of anything relying on this feature.
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
9:21 p.m.
+1
I would have proposed it but I was a bit afraid of it myself.
Caleb
On 05/16/2011 02:56 PM, Ludovic Dubost wrote:
Le 16/05/11 20:53, Sergiu Dumitriu a écrit :
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
+1
I've no knowledge of anything relying on this feature.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 
11:14 p.m.
+0, I will have to trust you on that since I don't know this feature very well
On Mon, May 16, 2011 at 20:53, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
19 May
19 May
3:57 p.m.
+1, with the same comment.
JV.
On Mon, May 16, 2011 at 11:14 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
+0, I will have to trust you on that since I don't
know this feature very well
On Mon, May 16, 2011 at 20:53, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5:15 p.m.
+1, not aware of any usage of that very old feature
Denis
On Thu, May 19, 2011 at 15:57, Jean-Vincent Drean <jean-vincent(a)drean.org>wrote;wrote:
+1, with the same comment.
JV.
On Mon, May 16, 2011 at 11:14 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
+0, I will have to trust you on that since I
don't know this feature very
well
On Mon, May 16, 2011 at 20:53, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
17 May
17 May
7:34 a.m.
On May 16, 2011, at 8:53 PM, Sergiu Dumitriu wrote:
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
+1 (same as Thomas I have no knowledge of that "feature").
Thanks
-Vincent
9:45 a.m.
+1
Jerome
On Mon, May 16, 2011 at 8:53 PM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
20 May
20 May
2:35 p.m.
+1
Thanks,
Marius
On 05/16/2011 09:53 PM, Sergiu Dumitriu wrote:
Hi devs,
In the early days of XWiki, XClass definitions were stored in the
database exploded into several tables, as object-relational mapping of
the BaseClass and the related PropertyClasses. That code still exists,
and can be enabled in the configuration.
The alternative, which has been used as the default even before 1.0, is
to store the class as an XML blob, since it doesn't make much sense to
have the class definition available in the database as objects.
Since the default has been to store the classes as XML, the old code
hasn't been tested in years, and I'm not even sure it still works. I'd
like to remove that code completely. This involves:
- pruning several methods and if-else branches from XWikiHibernateStore
- removing several class mappings, thus tables from the database (we're
not going to actually delete existing tables, just that they won't be
created in new installations)
WDYT? Is anybody actually relying on this feature?
My +1 to proceed with this cleanup.
4868
days inactive
4872
days old
8 comments
9 participants
participants (9)
-
Caleb James DeLisle -
Denis Gervalle -
Jean-Vincent Drean -
Jerome Velociter -
Ludovic Dubost -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol