<?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: Search Cursor vs Selection in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/search-cursor-vs-selection/m-p/277697#M21437</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try it and time it....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Sep 2019 14:02:45 GMT</pubDate>
    <dc:creator>JoeBorgione</dc:creator>
    <dc:date>2019-09-23T14:02:45Z</dc:date>
    <item>
      <title>Search Cursor vs Selection</title>
      <link>https://community.esri.com/t5/python-questions/search-cursor-vs-selection/m-p/277695#M21435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anybody tested if one is faster than the other? Say you have 300,000 records to go through and you want to find all the records that have nulls in a field, would selecting with a "IS NULL" where clause be faster than a search cursor running through? Or would the difference be negligible?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Sep 2019 13:18:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/search-cursor-vs-selection/m-p/277695#M21435</guid>
      <dc:creator>MKF62</dc:creator>
      <dc:date>2019-09-23T13:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: Search Cursor vs Selection</title>
      <link>https://community.esri.com/t5/python-questions/search-cursor-vs-selection/m-p/277696#M21436</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Select Layer By Attribute will be, or should be, significantly faster since it is both compiled code as well as it pushes the execution to the data store tier closer to the data itself.&amp;nbsp; That said, for 300,000 records I am not sure it makes a big difference either way.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Sep 2019 13:52:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/search-cursor-vs-selection/m-p/277696#M21436</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2019-09-23T13:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: Search Cursor vs Selection</title>
      <link>https://community.esri.com/t5/python-questions/search-cursor-vs-selection/m-p/277697#M21437</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try it and time it....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Sep 2019 14:02:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/search-cursor-vs-selection/m-p/277697#M21437</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2019-09-23T14:02:45Z</dc:date>
    </item>
  </channel>
</rss>

