Timeline for Python Script updating default version and child version simultaneously
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2018 at 19:19 | comment | added | user125266 | @Simon.y That's what I normally use. I'm glad you told me. This will be useful for me later on. Generally I use a connection file to make a path to the feature class I want to edit or update that I actually can edit/update. I assign my version to that parameter, and if I need to I use the make table view change version trick. There's way too much overhead involved in messing with enterprise connections with arcpy. | |
| Aug 29, 2018 at 19:15 | comment | added | Simon.y | My understanding is that using SQL does not track the adds and deletes to a specific version, it is hitting the table that the version is referencing. If you notice I don't even start and edit session, even if I am editing the Table View (_evw) in SQL Server, the database has not been told to track changes. I gave up on using ArcSDESQLExecute after looking more into it. If memory serves it was not intended to perform updates but to do more database maintenance tasks. I ended up using UpdateCursors to do this which was much easier, and it processes much faster! | |
| Aug 29, 2018 at 19:11 | comment | added | Simon.y | Hi @Steve, it has been a long time since I thought about this but I am fairly sure that my Database Connection was already hitting the version I wanted to update. That is why I named it DevVersion and not just Dev, but I have long since deleted that file. That is a useful note about the MakeTableView for changing versions. | |
| Aug 29, 2018 at 16:58 | history | answered | user125266 | CC BY-SA 4.0 |