From: Andrzej J. T. <an...@ch...> - 2010-03-31 14:14:07
|
Adam said: > This is quite exciting - I like :-) I agree...the concept is intriguing. > And the database configuration could again be defined in conf.xml > files in the /sql/system/sql collections. Caching and connection > property characteristics could also be placed in conf.xml files in the > appropriate sql configuration collection. I think this is not a feature that will be of general interest to all eXist users, and should not be part of the core.....an external extension/plugin would make more sense, so that those that want to integrate with a RDBMS can just install the plugin and get the integration functionality. In that regard, I think the configuration should stay out of the main conf.xml and be put somewhere else, specific to the extension module. My 2 cents worth. > Almost all of the existing infrastructure could be reused. You would > simply need to extend the Collection function so that in the case of a > "/sql" collection it defered the document set building to code that is > very similar to that of the sql module. You would also need to come up > with a collection xml serialization scheme for displaying the > available sql schemas and tables as sub-collections but thus should > not be very hard and should be as close to possible (if not the same) > as the existing ones for the db collections. One thing to keep in mind is that processing of in-memory fragments (which would be created from the xml data coming from the RDBMS) are much slower than native xml documents stored in eXist. Maybe this will provide some impetus to optimize processing of in-memory fragments a bit more, which would be a "good thing". ;-) -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |