Problem
We recently documented the following changes:
- XPO may throw OverflowException if String or Byte Array value length (size) is greater than the maximum allowed database column size
- XPO may throw InvalidCastException or SqlExecutionErrorException if parameter types (for update/read queries) do not match database column types
Unfortunately, we failed to anticipate the scope of query parameter inconsistencies within customer apps (EAP/Beta feedback did not uncover this issue). Despite benefits associated with our changes, we do not want to force XPO users to modify their code immediately or revert to previous behavior manually (with feature toggles).