Dare Obasanjo wrote
...,
>
> is added as well as an error code be added in ErrorCodes such as
>
> UNSUPPORTED_RESOURCE_TYPE
>
> which can be one of the specified error codes when an XMLDBException is
thrown
> from a
>
> Collection#storeResource( )
>
> call. That is if this is the directio
Ron,
Actually "QName" refers to a namespace _qualified_ name, which need not be
prefixed.
Jonathan
- Original Message -
From: "Ronald Bourret" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 14, 2002 4:14 AM
Subject: Re: Resources and
An XML:DB "Resource" corresponds to a DOM "Node". The sub-type "XMLResource"
does directly correspond to a DOM Node, and hence supports the DOM Node
types.
Currently it is possible to support simple datatypes via this mechanism as
each of these datatypes has a textual representation, and hence can
Dare Obasanjo wrote:
> - Original Message -
> From: "Jonathan Borden" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, January 11, 2002 3:05 PM
> Subject: Re: Problems With Implementing XMLDB API
>
>
>
> > Err, so "
Jim Tivy wrote:
> Hi folks
>
> This thread has got me thinking. What is returned from a query is a
value.
> What is a legal value should be defined in the API spec. XQuery has
define
> what a legal value is in their data model doc (see w3c data model doc).
It
> may be wise to adopt this as a val
> >
> > so? you also cannot store a book where SQL expects an int.
> >
>
> Now I'm confused.
>
> What _good_ RDBMS API have you used that allows you to pass types that
aren't
> natively supported by the DB in update operations?
> Just to recap I'll rewrite
> the query that Kimbro agreed didn't mak
> The problem with this approach is that you have now created a Resource
that
> cannot be used in other situations where implementors of the Resource
> interface can such as
>
> storeResource(Resource res)
> Stores the provided resource into the database.
>
> in the Collection interface,
Actually rather than.
>
> interface SimpleTypeResource extends Resource {
> const STRING_TYPE = 1;
> const INTEGER_TYPE = 2;
> const FLOAT_TYPE = 3;
> const DATE_TYPE = 4;
> int getType();
> String getString();
> void setString();
> Integer getInteger() throws cast..
Dare Obasanjo wrote:
>
> From the point of view of an implementor the XPathService returns
Resources
> within ResourceSets and this is way too coarse grained. In fact I feel the
> concept of making ResourceSets the return value of XPath queries is a bad
idea
> for a few reasons
>
> 1.) It is incon
John Merrells wrote:
>
> > I really can't see how this might happen. You should always have an
> > executation context like XSLT or the like. We only use XPath to
> > evaluate the context node, i.e. select one or more node/elements.
> > But your're right here: this question just not come up before
Jim Tivy wrote:
> I would suggest that XInclude is an entirely different technology - more
> like an entity expansion.
It is fine to suggest this, but your suggestion provides no guidance to the
characteristics of this "entirely different technology". If you read my
reply to Paul, you should note
Paul Rabin wrote:
>
> At 10:11 AM 7/25/01 -0400, Jonathan Borden wrote:
>
> >Ok I understand that the attribute has a different name (that is one
> >difference). I still don't understand how it functions in a different
way.
> >In specific an implementation of XI
Paul Rabin wrote:
> At 11:36 PM 7/24/01 -0400, Jonathan Borden wrote:
>
> >Well assuming the attribute is "xml:include" then this is identical to
> >XInclude isn't it? Seriously, what is the essential difference between
this
> >'experimental
Paul Rabin wrote:
>
> At 06:15 PM 7/23/01 -0700, you wrote:
> >dbXML has autolinking which is pretty much a combination between
> XInclude
> >and XLink. It's just an experimental feature though and has issues in
> >relation to the current API. It's also of course specific to dbXML and
> >ties the i
Lars, Kimbro:
>
> On Wed, 13 Jun 2001 14:09:09 -0400
> Kimbro Staken <[EMAIL PROTECTED]> wrote:
>
> > Due to the way XPath and namespaces don't work very well together, the
> > current XPathQueryService does not work namespace aware queries. I'd
> > like some input on what the best way to solve t
Kimbro Staken wrote:
> Right now we have a method XMLResource.setContentAsSAX() that returns a
> ContentHandler that can be used to set the content of the resource. I'm
> wondering what are the real use cases for exposing this method? Clearly
> getContentAsSAX() is necessary and useful but I'm not
16 matches
Mail list logo
