We are exploring the viability of using branch versioning. Our organization utilizes SQL views for much of what we serve out to our portal as enrichment services. Looking over the structure of how the branch versioned tables are built, it appears we won't be able to call just a generic select statement to pull data from the base table, but will have to incorporate some heftier sql just to get the correct rows to return. Is this something that has been addressed and I've just missed it? Or does ESRI have a sample of the code needed to pull the current state of features in the default version?
We'd love to explore branch versioning, but if it removes support for database views (or over complicates them), it would be a real buzzkill.