But I do see it as a problem, which was the point I was
trying to make
with my Oracle example.
Ok. Sorry, for the misconception.
You and Dare are correct that Services tied
exclusively to collections are not intuitive and inadequate.
Understand
though that until I implemented the
On Friday, February 8, 2002, at 04:07 AM, Arno de Quaasteniet wrote:
I can imagine that you didn't see it before. I probably also wouldn't
have since X-Hive also has root collection :)
Anyway, if there is a problem then it has to be solved. I need to think
some more about you suggestions of
On Fri, 8 Feb 2002 04:40:57 -0700
Kimbro Staken [EMAIL PROTECTED] wrote:
It's widely used though, simply because dbXML, eXist and now Xindice use
it. It may not be used in any big installations, but it is definitely used
in a whole bunch of little ones.
I don't necessarily agree that it's
On Thursday, February 7, 2002, at 02:01 PM, Tom Bradford wrote:
Yes... and it shouldn't cause confusion because Services as they're
implemented at the moment can't be repointed to other Collections. To a
Service, the Collection provides context. It may be a starting context
for recursive
--- Tom Bradford [EMAIL PROTECTED] wrote:
On Thursday, February 7, 2002, at 02:09 PM, Kimbro
Staken wrote:
The problem comes if there is no root collection.
For instance I have
an Oracle 9i impl where the collection hierarchy
is flat. I had to
synthesize a root collection in order to
On Thursday, February 7, 2002, at 02:30 PM, Dare Obasanjo wrote:
This can easily be supported by doing what I did with
SiXDML. Just add getService(String, String) to the
Database class.
Here's the problem with that though. Imagine you have a program that
performs service requests in a generic
On Thursday, February 7, 2002, at 02:40 PM, Tom Bradford wrote:
On Thursday, February 7, 2002, at 02:30 PM, Dare Obasanjo wrote:
This can easily be supported by doing what I did with
SiXDML. Just add getService(String, String) to the
Database class.
Here's the problem with that though. Imagine
