Comments for www.xmldb.nl http://www.liberidu.com/blog About Oracle, XMLDB and other interests... Fri, 12 Sep 2014 15:02:57 +0000 hourly 1 http://wordpress.org/?v=4.0 Comment on Oracle Database 12.1.0.2.0 – Getting started with JSON Path Expressions by Marco Gralikehttp://www.liberidu.com/blog/2014/09/12/oracle-database-12-1-0-2-0-getting-started-with-json-path-expressions/comment-page-1/#comment-86452 Fri, 12 Sep 2014 15:02:57 +0000 http://www.liberidu.com/blog/?p=4675#comment-86452 BTW I distilled the SQLLoader/External Table etc syntax from post’s from Tim Hall here:

http://www.oracle-base.com/articles/10g/load-lob-data-using-sql-loader.php
http://www.oracle-base.com/articles/10g/ExternalTablesContainingLobData.php

]]>
Comment on Oracle Database 12.1.0.2.0 – Getting started with JSON Path Expressions by Marco Gralikehttp://www.liberidu.com/blog/2014/09/12/oracle-database-12-1-0-2-0-getting-started-with-json-path-expressions/comment-page-1/#comment-86413 Fri, 12 Sep 2014 13:29:48 +0000 http://www.liberidu.com/blog/?p=4675#comment-86413 Apparently the “wish” was something along the lines which was already considered (just asked). Let’s see how the “JPATH” (good abbreviation ;-) btw) evolves over the years. There will probably be a lot of discussions between JSON organizations and DB companies about “the road to travel”.

]]>
Comment on Oracle Database 12.1.0.2.0 – Getting started with JSON Path Expressions by Kim Berg Hansenhttp://www.liberidu.com/blog/2014/09/12/oracle-database-12-1-0-2-0-getting-started-with-json-path-expressions/comment-page-1/#comment-86344 Fri, 12 Sep 2014 11:19:52 +0000 http://www.liberidu.com/blog/?p=4675#comment-86344 Sure, I am not arguing that “JPATH” should be practically identical to “XPATH”, not at all. I am not even sure I would like my “wish” to be fullfilled, as that might be a step “in the wrong direction” for the development of JSON. It’ll depend on the way JSON standards will evolve. Maybe some day as there is “simple” XPath and “complex” XQuery, there might be similar (not identical) standards for querying JSON data – and if that happens in JSON standard, then presumably Oracle JSON functions will adapt such methods as they evolve.

My purpose in my post was mainly to show people used to XML_TABLE how they can do similar stuff with JSON_TABLE. Particarly as more and more webservices return JSON results these days, it is nice for an Oracle database developer to be able to utilize the results of such webservice calls as simply as we’ve previously been able to do it for webservices that return XML results.

]]>
Comment on Oracle Database 12.1.0.2.0 – Getting started with JSON Path Expressions by Marco Gralikehttp://www.liberidu.com/blog/2014/09/12/oracle-database-12-1-0-2-0-getting-started-with-json-path-expressions/comment-page-1/#comment-86342 Fri, 12 Sep 2014 11:14:23 +0000 http://www.liberidu.com/blog/?p=4675#comment-86342 BTW… Great post (http://dspsd.blogspot.dk/2014/09/jsontable-or-xmltable-comparison-with.html)!

8-)

]]>
Comment on Oracle Database 12.1.0.2.0 – Getting started with JSON Path Expressions by Marco Gralikehttp://www.liberidu.com/blog/2014/09/12/oracle-database-12-1-0-2-0-getting-started-with-json-path-expressions/comment-page-1/#comment-86335 Fri, 12 Sep 2014 11:03:10 +0000 http://www.liberidu.com/blog/?p=4675#comment-86335 Thanks Kim.

To be honest, were talking JSON now, not XML.

Initially I had the same notion as you, comparing the operators for the different realms at first as well, but in we are talking, in the case of JSON, about a new query standard which is still evolving. Oracle in conjunction with some other mayor DB / hardware supplier is working towards a new JSON database query standard (as mentioned in the slides). So in all, its new (and far from complete).

Therefore JSON_TABLE and XML_TABLE will be ending up completely different in behavior (they already do “NULL ON ERROR”?) and needs for the specific different kinds of data formats (and standards).

That said, I will point one of the developers in charge to this comment and your post to see if they (and the other company) find it feasible to implement such a functionality.

]]>