<?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 Row accessors using the index field in API 1.2 ? in File Geodatabase API Questions</title>
    <link>https://community.esri.com/t5/file-geodatabase-api-questions/row-accessors-using-the-index-field-in-api-1-2/m-p/380266#M638</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello, I have dowloaded the V1.2 FileGDB API.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was expecting this version to access the values �??�??in a row for field index as well as by name.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It is contemplated for the next versions?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In a previous thread it was commented...&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-style:italic;"&gt;...&lt;BR /&gt;In conclusion, it appears that the getter calls on attributes with the &lt;BR /&gt;FILEGDB API do have a significant performance cost (this is especially &lt;BR /&gt;true when there are a large number of attributes in the table). Fortunately&lt;BR /&gt;for your case, you have the option of recoding to delay the use of 'Get'&lt;BR /&gt;attribute accessors until they are actually necessary.&lt;BR /&gt;&lt;BR /&gt;I've recommended that a circular search algorithm be used in the getter&lt;BR /&gt;and setter functions, and that consideration be given to overloading the&lt;BR /&gt;Row accessors using an integer radix (vice name) which should give uniform &lt;BR /&gt;access cost without regard to the attribute retrieval order.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.arcgis.com/threads/33528-Slow-performance-reading-FGDB"&gt;http://forums.arcgis.com/threads/33528-Slow-performance-reading-FGDB&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thank you very much&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Mar 2012 20:09:12 GMT</pubDate>
    <dc:creator>ahuarte</dc:creator>
    <dc:date>2012-03-08T20:09:12Z</dc:date>
    <item>
      <title>Row accessors using the index field in API 1.2 ?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/row-accessors-using-the-index-field-in-api-1-2/m-p/380266#M638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello, I have dowloaded the V1.2 FileGDB API.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was expecting this version to access the values �??�??in a row for field index as well as by name.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It is contemplated for the next versions?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In a previous thread it was commented...&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-style:italic;"&gt;...&lt;BR /&gt;In conclusion, it appears that the getter calls on attributes with the &lt;BR /&gt;FILEGDB API do have a significant performance cost (this is especially &lt;BR /&gt;true when there are a large number of attributes in the table). Fortunately&lt;BR /&gt;for your case, you have the option of recoding to delay the use of 'Get'&lt;BR /&gt;attribute accessors until they are actually necessary.&lt;BR /&gt;&lt;BR /&gt;I've recommended that a circular search algorithm be used in the getter&lt;BR /&gt;and setter functions, and that consideration be given to overloading the&lt;BR /&gt;Row accessors using an integer radix (vice name) which should give uniform &lt;BR /&gt;access cost without regard to the attribute retrieval order.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.arcgis.com/threads/33528-Slow-performance-reading-FGDB"&gt;http://forums.arcgis.com/threads/33528-Slow-performance-reading-FGDB&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thank you very much&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2012 20:09:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/row-accessors-using-the-index-field-in-api-1-2/m-p/380266#M638</guid>
      <dc:creator>ahuarte</dc:creator>
      <dc:date>2012-03-08T20:09:12Z</dc:date>
    </item>
    <item>
      <title>Re: Row accessors using the index field in API 1.2 ?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/row-accessors-using-the-index-field-in-api-1-2/m-p/380267#M639</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We are aware of this discussion, but we have not committed to an investigation as to whether there is in fact a problem and that the proposed change would improve performance.&amp;nbsp; It is on a list of things we may look into eventually.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Mar 2012 15:57:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/row-accessors-using-the-index-field-in-api-1-2/m-p/380267#M639</guid>
      <dc:creator>DavidSousa</dc:creator>
      <dc:date>2012-03-09T15:57:02Z</dc:date>
    </item>
    <item>
      <title>Re: Row accessors using the index field in API 1.2 ?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/row-accessors-using-the-index-field-in-api-1-2/m-p/380268#M640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;ok, thank you very much. Expectant hope &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I tried to read a FGDB with the new version and the time is the same as the previous one. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I know that is not a usual case, but the implementation for read values by index field I think it would be easy especially when the row class has members with that information.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you very much for the answer.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Mar 2012 07:37:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/row-accessors-using-the-index-field-in-api-1-2/m-p/380268#M640</guid>
      <dc:creator>ahuarte</dc:creator>
      <dc:date>2012-03-10T07:37:32Z</dc:date>
    </item>
  </channel>
</rss>

