build a sentient computer smarter than I am.
- Original Message -
From: Jonathan Borden [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, January 12, 2002 8:33 PM
Subject: Re: Problems With Implementing XMLDB API
Dare Obasanjo wrote:
- Original Message -
From: Jonathan Borden
API
- 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 addResource on a BinaryResource is OK _from an
interface point of
view_ when addResource
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Dare Obasanjo
Sent: Saturday, January 12, 2002 7:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Problems With Implementing XMLDB API
The valid return types from an XQuery query are XML schema types while
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 valid
- Original Message -
From: Jonathan Borden [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, January 12, 2002 8:11 PM
Subject: Re: Problems With Implementing XMLDB API
Exactly, the XQuery 1.0 and XPath 2.0 data models have merged. If XML:DB is
really going to be the standard API
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 addResource on a BinaryResource is OK _from an interface point
of
view_ when
.
- Original Message -
From: Jonathan Borden [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, January 12, 2002 8:33 PM
Subject: Re: Problems With Implementing XMLDB API
Dare Obasanjo wrote:
- Original Message -
From: Jonathan Borden [EMAIL PROTECTED]
To: [EMAIL PROTECTED
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 make sense that
- 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 addResource on a BinaryResource is OK _from an interface point of
view_ when addResource on an integer
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...
- Original Message -
From: Kimbro Staken [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 11, 2002 8:48 AM
Subject: Re: Problems With Implementing XMLDB API
You're right in many cases that won't make sense, that doesn't have to be
the case though. The resource instance
On Thursday, January 10, 2002, at 06:57 PM, John Merrells wrote:
It seems that somewhere along the line whoever designed the XML:DB API
decided
that XPath queries should return ResourceSets which seem to map to very
coarse
grained database objects like XML documents and BLOBs even though XPath
On Thursday, January 10, 2002, at 09:37 PM, Dare Obasanjo wrote:
Hi,
I'm working on implementing Core Level 0 compliance over an NXD as
part of
a project I'm working on and have bumped against a problem.
Please use the [EMAIL PROTECTED] mailing list for discussions about the
API.
It seems
- Original Message -
From: Kimbro Staken [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 10, 2002 6:06 PM
Subject: Re: Problems With Implementing XMLDB API
It seems that somewhere along the line whoever designed the XML:DB API
decided
On Thursday, January 10, 2002, at 11:04 PM, 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
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, since
- Original Message -
From: Jonathan Borden [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 11, 2002 2:38 PM
Subject: Re: Problems With Implementing XMLDB API
so? you also cannot store a book where SQL expects an int.
Now I'm confused.
What _good_ RDBMS API have you
17 matches
Mail list logo
