[
Lists Home |
Date Index |
Thread Index
]
This is one of those few times I agree with Dare :-)) even though we
work for the same company. He points out one of the big challenges.
Couple of comments:
If we are querying over a bunch of back-end relational databases, why is
XQuery better than some flavor of SQL? At least the type system
mismatch could be manageable.
Honestly, whether we use a SQL DQP or XQuery DQP is not the biggest
problem. Semantic and structural mismatches, data quality, policies
around running arbitrary queries on mission critical data stores, data
volume, updates, security and access control and metadata management are
the bigger problems.
EII companies have come and gone, and new ones keep spawning every day.
Of the bigger companies around, It would be interesting to hear from
Dana and Denise Draper on this topic. Both of them have implemented
one.
Soumitra
-----Original Message-----
From: Dare Obasanjo [mailto:dareo@microsoft.com]
People keep saying this as if it so trivial. Basically all you've
described is what Crystal Reports does today but you've substituted SQL
for with XQuery. However due to the fact that XQuery + XSD have a
significantly different type system from your underlying relational or
other data stores this causes for interesting impedence mismatch when
performing queries.
|
