Menu

#4966 (ok 4.5) MySQL constraint violation errors are not shown when DebugSQL is on

4.4.10
resolved
None
Normal
2015-06-22
2015-06-22
No

Go to sakila (db strcuture) and try deleting film table with foreign key constraints enabled. Table should not be deleted since foreign key constraints prevent that from happening. However, row corresponding to film table is removed and upon refreshing appears again.

Discussion

  • Madhura Jayaratne

    • Group: Latest_Git --> 4.4.10
     
  • Madhura Jayaratne

    • summary: MySQL constraint violation errors are not shown --> MySQL constraint violation errors are not shown when DebugSQL is on
     
  • Madhura Jayaratne

    When DebugSQL is on, PMA_DatabaseInterface::getError() is called to record if there is an error. This calls PMA_DatabaseInterface::formatError() to format error message if there is in fact an error. However, formatError() issues a new query to get the variable 'language' which erases the original error message causing this bug

     
  • Madhura Jayaratne

    • summary: MySQL constraint violation errors are not shown when DebugSQL is on --> (ok 4.5) MySQL constraint violation errors are not shown when DebugSQL is on
    • status: open --> resolved
     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.