> Interesting question. When we created the API there was no way to add > collections at all. The CollectionManagementService was added later and it > assumes that there is always some kind of collection to start from. > Creating collections is a sticky problem overall because the existing > databases are pretty different in this regard. That is the main reason it > was pretty much left out. Can you assume a virtual root of some type that > can be used for a starting point?
That's a pretty good idea. I'll probably need to export some system collections that contain configuration information, and schema and stuff. But, it seems odd that this service is on Collection, as it would seem more natural on Database. The CollectionManagementService (CMS) interface inherits from Service which includes the SetCollection method. This presumably selects the focus of the Service... but this doesn't seem to make sense for CMS as both methods take the name of the collection to operate on. I'd be tempted to add a getService method to Database. John _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
