I am trying to edit a FeatureClass in a specific version of the GeoDatabase through SQL using versioned views. I call edit_version and send in the version name and "1" to start editing from one connection to the database. I open another connection to the database and call edit_version with the version name and "1", which ends up returning the following error
Msg 50000, Level 16, State 1, Procedure edit_version, Line 208
Lock conflict detected for state 26
Does this mean that a version can only be edited from one session at a time? Is this a limitation of editing geodatabases through SQL? This means that geodatabase versions cannot be edited by web applications. Since ArcMAP allows two users to edit the same version, does it mean that it is not a limitation if using the ArcObjects SDK?