ArcGIS Enterprise (ArcGIS Pro 3.0.1): Why versioned feature classes with “branch” type get uneditable?

[JamalNUMAN]

ArcGIS Enterprise (ArcGIS Pro 3.0.1): Why versioned feature classes with “branch” type get uneditable?

I couldn’t figure out why versioned feature classes with “branch” type get uneditable

Is this by design?

[JamalNUMAN]

This is very helpful.

Then the branch versioning comes to resolve the performance issues acknowledged in traditional versions. This suggests that the branch versions “technology” should be much more performant (faster) than the traditional when it comes to editing, searching, and querying.

Is this accurate?

[ScottTansley3]

i haven't baselined it between the two types to find the performance difference, but yes, in essence that is why Esri introduced this type of versioning.  Instead of spanning multiple database tables (i.e. featureclass, a, d, h etc) all of the data is held in one table and made live, archived or 'in a version' by the use of dates and other 'flags'.  Having everything in one table optimises the performance.