<?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: What does the E stand for in multiversioned _EVW view name? in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/what-does-the-e-stand-for-in-multiversioned-evw/m-p/1598890#M9525</link>
    <description>&lt;P&gt;I like edit&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;....... or "enterprise", I honestly have no idea.&lt;/P&gt;&lt;P&gt;I do remember when they started to add the "e" around 10.1/2'ish time frame. Before that it was just a "_vw" which people would also name their custom DB views so it could be confusing on which ones were "versioned" in the enterprise geodatabase.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Mar 2025 10:23:08 GMT</pubDate>
    <dc:creator>George_Thompson</dc:creator>
    <dc:date>2025-03-25T10:23:08Z</dc:date>
    <item>
      <title>What does the E stand for in multiversioned _EVW view name?</title>
      <link>https://community.esri.com/t5/geodatabase-questions/what-does-the-e-stand-for-in-multiversioned-evw/m-p/1598851#M9524</link>
      <description>&lt;P&gt;&lt;EM&gt;ArcGIS Pro 2.9.5 Oracle 18c 10.7.1 EGDB; traditional versioning moving edits to base&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;What does the “E” stand for in the autogenerated view "..._EVW" naming convention?&lt;/P&gt;&lt;P&gt;I have a vague memory that the E stands for “editioned” views. But that might not be right. "Edit"?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Mar 2025 13:05:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/what-does-the-e-stand-for-in-multiversioned-evw/m-p/1598851#M9524</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2025-03-25T13:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: What does the E stand for in multiversioned _EVW view name?</title>
      <link>https://community.esri.com/t5/geodatabase-questions/what-does-the-e-stand-for-in-multiversioned-evw/m-p/1598890#M9525</link>
      <description>&lt;P&gt;I like edit&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;....... or "enterprise", I honestly have no idea.&lt;/P&gt;&lt;P&gt;I do remember when they started to add the "e" around 10.1/2'ish time frame. Before that it was just a "_vw" which people would also name their custom DB views so it could be confusing on which ones were "versioned" in the enterprise geodatabase.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Mar 2025 10:23:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/what-does-the-e-stand-for-in-multiversioned-evw/m-p/1598890#M9525</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2025-03-25T10:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: What does the E stand for in multiversioned _EVW view name?</title>
      <link>https://community.esri.com/t5/geodatabase-questions/what-does-the-e-stand-for-in-multiversioned-evw/m-p/1599044#M9526</link>
      <description>&lt;P&gt;Although George's guess of "enterprise" is reasonable, my money is on "esri," with a very small chance "enhanced."&lt;/P&gt;&lt;P&gt;The earliest mentions of "multiversioned views" that I recall are from ArcGIS 9.2, which coincidentally the ArcGIS 9.2 Desktop Help is still available online (kudos to Esri for keeping the historical record alive online).&amp;nbsp; From &lt;A href="https://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=Using_multiversioned_views" target="_self"&gt;&lt;SPAN&gt;ArcGIS Desktop Help 9.2 - Using multiversioned views&lt;/SPAN&gt;&lt;/A&gt;:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;H3&gt;What are multiversioned views?&lt;/H3&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;Multiversioned views incorporate database views, stored procedures, triggers, and functions to access a specified version of data in a geodatabase table using structured query language (SQL).&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;In the early days, the documentation suggested using either a "mv_" prefix or "_mv" suffix:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;OL&gt;&lt;LI&gt;At a command prompt, execute the sdetable function to create a multiversioned view.&lt;/LI&gt;&lt;/OL&gt;&lt;PRE&gt;sdetable –o create_mv_view –T permits_mv –t permits –i 4400 –D code –u sarja –p not4u&lt;/PRE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The "mv" prefix or suffix made sense given the name of the feature was "multiversioned view."&amp;nbsp; However, around that same time "mv" started becoming associated with "materialized views."&amp;nbsp; As important as geodatabases may be to us GIS users, the non-spatial use of databases dominates the spatial use of databases, so most people in the database world would associate "mv" with "materialized view" and not "multiversioned view."&amp;nbsp;&lt;/P&gt;&lt;P&gt;There was a brief period after transitioning from "mv" where Esri adopted "vw," which is a standard suffix or prefix for any database view.&amp;nbsp; I believe it was also around this same time that Esri moved away from "multiversioned views" and starting use just "versioned views."&amp;nbsp; Although "vv" is a logical abbreviation for "versioned view," my guess is people didn't like it because it might be too easy for people to confuse "vv" for "w".&lt;/P&gt;&lt;P&gt;Similar to Esri JSON, Esri JS, and other standard terms that Esri prefixes with their name, my guess is that "e" in "evw" is for Esri.&amp;nbsp; Also, the change from "SDE" to "Enterprise geodatabase (EGDB)" came many years after the switch to "evw" so I don't think the word "enterprise" was the motivation.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Mar 2025 15:59:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/what-does-the-e-stand-for-in-multiversioned-evw/m-p/1599044#M9526</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2025-03-25T15:59:04Z</dc:date>
    </item>
  </channel>
</rss>

