/
Historical Oracle vs. MySQL Issues

Historical Oracle vs. MySQL Issues

Owned by Barb Sutton (Deactivated)
Last updated: Sept 15, 2015

This page lists some of the differences we've seen historically between Oracle and MySQL within KFS.

Oracle vs. MySQL

  • The empty string is treated differently (see KFSMI-562)
  • Sorting involving nulls works differently (see KULPURAP-2037)
  • Avoiding class cast exceptions when getting a count (see KULRNE-6028)
  • MySQL gets mad when columns in a parent/child relationship are different lengths (see KULDBA-1167)
  • Initially, we had a column default for obj_id in Oracle, but since we couldn't do the same in MySQL, it was removed. (KULDBA-1169)

Related content