Reconciling versions makes both target and source(s) point to the same state. I have an arcpy script that essentially will create a version from a parent of the db - in a state that is empty - adds data to the feature classes, and then will append them to its parent's parent.
So its immediate parent is still pointing at a state that is empty. But now the child and the one it is merging with(state above its parent) are both point to a version that has a lot of data. Ideally, I would like a way to keep the child version just have the data that was loaded to it. Essentially have the child contain only data that came in during that process.
This seems like it should be a thing and would be a quick way to copy a lot of data to a version without the use of any cursors. I found this post When Versioning with ArcSDE can posted edits be cancelled or rejected? and it talks about editing the sde versions table. Hoping there is another option. However is there a clean way of changing the state using ArcPy? I am thinking, if I have to, I will just connect with pyodbc and then change the table.
Also, is it 100% that when a database version is created and then immediately reconciled without any other users or transactions happening, that its state will only one ahead of its creation?