<?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>idea parseWhereClause ('@arcgis/core/core/sql.js') should return the parsed where clause in ArcGIS JavaScript Maps SDK Ideas</title>
    <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/parsewhereclause-arcgis-core-core-sql-js-should/idi-p/1693355</link>
    <description>&lt;P&gt;It seems to me that it would be useful if `&lt;SPAN&gt;parseWhereClause` from `&lt;/SPAN&gt;&lt;SPAN&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/642472"&gt;@ArcGIS&lt;/a&gt;/core/core/sql.js` returned the actual parsed where clause as a property of the returned `WhereClause` object, or via its `toString()` method.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This would allow a developer to actually use that parsed string as the where clause in their query or definition expression. It would presumably be well-formed, trimmed, white-space removed, etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The function: &lt;A href="https://developers.arcgis.com/javascript/latest/references/core/core/sql/#parseWhereClause" target="_blank"&gt;https://developers.arcgis.com/javascript/latest/references/core/core/sql/#parseWhereClause&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The returned object:&amp;nbsp;&lt;A href="https://developers.arcgis.com/javascript/latest/references/core/core/sql/WhereClause/" target="_blank"&gt;https://developers.arcgis.com/javascript/latest/references/core/core/sql/WhereClause/&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Anyone using this function would likely be interested in using (or at least seeing) the parsed string.&amp;nbsp;&lt;SPAN&gt;Currently, you can only "ask" this function about your where clause: Is it standardized? What fields does it have? Will it work for this query? Presumably, you could build the query yourself from the `parseTree` property, but that seems like a chance to introduce errors after you've called the function.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But there's definitely one thing you don't get when you call `parseWhereClause`: the parsed where clause.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Mar 2026 13:05:17 GMT</pubDate>
    <dc:creator>DanRussell</dc:creator>
    <dc:date>2026-03-30T13:05:17Z</dc:date>
    <item>
      <title>parseWhereClause ('@arcgis/core/core/sql.js') should return the parsed where clause</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/parsewhereclause-arcgis-core-core-sql-js-should/idi-p/1693355</link>
      <description>&lt;P&gt;It seems to me that it would be useful if `&lt;SPAN&gt;parseWhereClause` from `&lt;/SPAN&gt;&lt;SPAN&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/642472"&gt;@ArcGIS&lt;/a&gt;/core/core/sql.js` returned the actual parsed where clause as a property of the returned `WhereClause` object, or via its `toString()` method.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This would allow a developer to actually use that parsed string as the where clause in their query or definition expression. It would presumably be well-formed, trimmed, white-space removed, etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The function: &lt;A href="https://developers.arcgis.com/javascript/latest/references/core/core/sql/#parseWhereClause" target="_blank"&gt;https://developers.arcgis.com/javascript/latest/references/core/core/sql/#parseWhereClause&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The returned object:&amp;nbsp;&lt;A href="https://developers.arcgis.com/javascript/latest/references/core/core/sql/WhereClause/" target="_blank"&gt;https://developers.arcgis.com/javascript/latest/references/core/core/sql/WhereClause/&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Anyone using this function would likely be interested in using (or at least seeing) the parsed string.&amp;nbsp;&lt;SPAN&gt;Currently, you can only "ask" this function about your where clause: Is it standardized? What fields does it have? Will it work for this query? Presumably, you could build the query yourself from the `parseTree` property, but that seems like a chance to introduce errors after you've called the function.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But there's definitely one thing you don't get when you call `parseWhereClause`: the parsed where clause.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 13:05:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/parsewhereclause-arcgis-core-core-sql-js-should/idi-p/1693355</guid>
      <dc:creator>DanRussell</dc:creator>
      <dc:date>2026-03-30T13:05:17Z</dc:date>
    </item>
  </channel>
</rss>

