[xwiki-devs] [VOTE] Remove the xclass database mapping
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/
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
+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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+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 <[email protected]> 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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1, with the same comment. JV. On Mon, May 16, 2011 at 11:14 PM, Thomas Mortagne <[email protected]> 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 <[email protected]> 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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1, not aware of any usage of that very old feature Denis On Thu, May 19, 2011 at 15:57, Jean-Vincent Drean <[email protected]>wrote:
+1, with the same comment.
JV.
On Mon, May 16, 2011 at 11:14 PM, Thomas Mortagne <[email protected]> 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 <[email protected]> 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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
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
+1 Jerome On Mon, May 16, 2011 at 8:53 PM, Sergiu Dumitriu <[email protected]> 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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+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.
participants (9)
-
Caleb James DeLisle -
Denis Gervalle -
Jean-Vincent Drean -
Jerome Velociter -
Ludovic Dubost -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol