D
dbeavon
Guest
Thanks Fernando. I am optimistic for a resolution to that open bug. I have an open case related to the larger issue - finding out if/when CRC's are exclusively used to disqualify programs from being executed. I think this is still a topic of confusion. I'll definitely follow up and let you know what comes out of that case. According to that KB article, (000010488, What Metaschema fields are involved in table and database CRC calculations) it seems that CRC's will now play a subordinate role in determining if r-code is compatible. CRC's no longer create an error condition or, by themselves, prevent code from running on a given database. The "extra runtime check" is apparently what really matters (going forward). From what I can tell, it looks like we've reached a tipping point in the old "CRC"-based strategy. Progress has continually relaxed previous constraints which had inhibited online dictionary changes, notably those kinds of changes made dynamically via SQL DML and those not requiring exclusive schema locks. The expectation I have is that I should be able to (1) export my schema definitions from a source database to a schema-only database, (2) compile against it and then, (3) the result should be r-code that is compatible with the source. This is not something that was possible until the very most recent releases of OE. My recollection is that the scenario was prevented because of some of the more unusual OE schema internals (OE _field-rpos holes etc - things which aren't exposed very well, and whose values can't be influenced easily by a developer).
Continue reading...
Continue reading...