Bug Report #3404

Error creating Exception object for SQLSTATE[42S22]: Column not found: 1054

Added by money mark over 3 years ago. Updated over 3 years ago.

Status:ClosedStart date:11/18/2010
Priority:NormalDue date:
Assignee:Woody Gilk% Done:

100%

Category:-
Target version:Kohana v3.x - v3.0.10
Resolution:fixed Points:

Description

Kohana 3.0.8 is currently failing to create the Exception object when an un-handled SQLSTATE[42S22]: Column not found: 1054 error is thrown by the DB driver. The issue appears to occur because the value '42S22' is passed as the numeric code, which fails to then parse properly as a numeric value, throwing the following exception in the log:

ErrorException [ 8 ]: A non well formed numeric value encountered ~ SYSPATH\classes\kohana\exception.php [ 30 ]

This error was encounted against MYSQL 5.5.7.


Related issues

Related to Database - Bug Report #3358: pdo Database_Exception vs pgsql Closed 10/29/2010
Related to Database - Bug Report #3704: Database error codes are inaccessible without parsing the... Closed 02/06/2011
Duplicates Kohana v3.x - Bug Report #3927: Kohana_Exception should handle non-integer codes Closed 04/16/2011

Associated revisions

Revision f2e5662d
Added by Woody Gilk over 3 years ago

Moving all error codes into messages for Database_Exception calls, fixes #3404

Revision 539c81c3
Added by Chris Bandy over 3 years ago

Revert "Moving all error codes into messages for Database_Exception calls, fixes #3404" Refs #3927

This reverts commit f2e5662d373e8d5847ee12c3e27c8210500bb5d2.

History

#1 Updated by Woody Gilk over 3 years ago

  • Target version changed from v3.0.9 to v3.0.10

#2 Updated by Kiall Mac Innes over 3 years ago

  • Project changed from Kohana v3.x to Database
  • Category deleted (Core)

#3 Updated by Woody Gilk over 3 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

#4 Updated by Woody Gilk over 3 years ago

  • Resolution set to fixed

Also available in: Atom PDF