cyclical redundancy check

[HarryBrock]

I have beentesting something for the last hour and it seems to work....but am thinking Idid something wrong.

Say I a database and a window to update a table in the database.

1. I compile the code
2. I add a new index to the table being updated... (This should change the csc)
3. I only run the .r files and it works like it should.

I was thinking that adding an index (changingthe database) would stop the .r file from running and would need to be recompiled.

Am I overlooking something here? I am using OpenEdge 10.2A

 

[TomBascom]

This is expected behavior.

Adding objects (tables, fields & indexes) no longer invalidates the CRC and can be done online.

 

[andre42]

This is expected behavior.

Adding objects (tables, fields & indexes) no longer invalidates the CRC and can be done online.

To be more precise:

• In which Progress version did adding tables invalidate any CRCs? I started with Progress 9 so I don't know if this was the case with older versions.
• Adding fields still changes the CRC, but OpenEdge is recently (10.2B?) able to cope with added fields without throwing a CRC error.
• Indexes got their own CRCs with Progress 9, so adding a new index doesn't change the CRC of an existing object anymore.

Being able to do a schema change online is another matter. With OpenEdge it became possible to add objects online (tables & fields, I think this is still not possible with indexes), but adding fields still changed the table CRC and required a recompile.