<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Support for NXQL &amp;apos;ORDER BY ecm:path&amp;apos; in the CoreSession.queryAndFetch API  in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321445#M8446</link>
    <description>&lt;P&gt;I agree. Yet the NXQL Documentation includes numerous references to CoreSession.queryAndFetch API enhancements/restrictions like this one. Would you consider including the following clause in the NXQL ecm&lt;/P&gt;</description>
    <pubDate>Mon, 29 Aug 2016 14:52:39 GMT</pubDate>
    <dc:creator>rg1_</dc:creator>
    <dc:date>2016-08-29T14:52:39Z</dc:date>
    <item>
      <title>Support for NXQL &amp;apos;ORDER BY ecm:path&amp;apos; in the CoreSession.queryAndFetch API</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321443#M8444</link>
      <description>&lt;P&gt;It seems reasonable that the CoreSession.queryAndFetch API would not support the NXQL 'ORDER BY ecm:path' clause. If this is the intended behavior, then the NXQL documentation should be updated to include this restriction.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2016 10:39:57 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321443#M8444</guid>
      <dc:creator>rg1_</dc:creator>
      <dc:date>2016-08-26T10:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: Support for NXQL &amp;apos;ORDER BY ecm:path&amp;apos; in the CoreSession.queryAndFetch API</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321444#M8445</link>
      <description>&lt;P&gt;It's not really a NXQL restriction but a restriction of this particular API&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2016 09:47:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321444#M8445</guid>
      <dc:creator>Florent_Guillau</dc:creator>
      <dc:date>2016-08-29T09:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Support for NXQL &amp;apos;ORDER BY ecm:path&amp;apos; in the CoreSession.queryAndFetch API</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321445#M8446</link>
      <description>&lt;P&gt;I agree. Yet the NXQL Documentation includes numerous references to CoreSession.queryAndFetch API enhancements/restrictions like this one. Would you consider including the following clause in the NXQL ecm&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2016 14:52:39 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321445#M8446</guid>
      <dc:creator>rg1_</dc:creator>
      <dc:date>2016-08-29T14:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: Support for NXQL &amp;apos;ORDER BY ecm:path&amp;apos; in the CoreSession.queryAndFetch API</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321446#M8447</link>
      <description>&lt;P&gt;Thanks for the remarks, I updated the doc.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2016 15:16:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/support-for-nxql-apos-order-by-ecm-path-apos-in-the-coresession/m-p/321446#M8447</guid>
      <dc:creator>Florent_Guillau</dc:creator>
      <dc:date>2016-08-29T15:16:44Z</dc:date>
    </item>
  </channel>
</rss>

