Mike Matrigali wrote:

I do wonder if there would be value to only apply the new options to 10.3 databases. Should we maintain exact compatibility in the soft
upgrade case?

I tend to think it is better to have the new behavior even in soft upgrade mode. The model normally is to test your application in soft upgrade and then hard upgrade if all went well. If the new behaviour is masked until hard upgrade, there is no option to go back, so I'd rather see the hit on soft upgrade, but I can see the other point of view. I agree that the incompatibility is a justified incompatibility and upgrade risk if sql authorization is used.

Kathey




Reply via email to