For those that missed it, Ipedo announced some exciting new XQuery View capabilities last week, just as XQuery 1.0 became an official standard (you can see my entry on that here.)
Anyway, I thought I'd summarize what we announced. We think XQuery is going to have an even bigger impact now that the "When will it become a standard" question is out of the way. Here are the high points:
- Processing of XML Stored in Relational Databases
- Ipedo's XQuery can be used in conjunction with the XML processing and
XQuery now available in Oracle 10g, DB2, and Microsoft SQL Server.
- XQuery View Caching
- Ipedo XIP allows XQuery Views results to be cached natively in XML,
providing both faster access for users, and post-processing and
drilldown using XQuery.
- Streaming Result Processing
- The new XQuery engine implements query operators that stream data
values, ensuring that query evaluation is memory efficient and allowing
clients to cursor through results at the lowest computation costs.
- Publishing of XQuery Views as Web Services
- XQuery Views can now be invoked directly via a Web Services API,
making it easy to create advanced data services. Ipedo XIP can
automatically generate the WSDL file needed for a particular XQuery
View.
- Extension Mechanisms for Custom Data Sources - In addition to standard data sources, Ipedo's XQuery extension framework now makes it possible for users to make custom data sources, such as in-house applications accessed using custom APIs.
Srinivas Pandrangi shows a simple example of using XQuery Views in his latest post over in The EII Files.
Comments