Skip Menu |

This queue is for tickets about the DBIx-Class CPAN distribution.

Report information
The Basics
Id: 35940
Status: rejected
Priority: 0/
Queue: DBIx-Class

People
Owner: Nobody in particular
Requestors: libithashanmugam [...] yahoo.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.08010
Fixed in: (no value)



Subject: 'Can't call method "resolve" on an undefined value' for all failures
Hi, We upgraded DBIx-Class from 0.07002 to the latest version, 0.08010 and found that the error messages thrown don't provide actual reason when connect/insert/update fails. I have a table 'user' with two fields id and email. id is the primary key. The following code should throw error for create failure due to unique constraint violation: my $user = $db->resultset('User')->create({id => 'slj', email => 'slj@yahoo.com'}); $user = $db->resultset('User')->create({id => 'slj', email => 'slj@yahoo.com'}); Error message thrown by latest version of DBIx-Class: ===================================== Can't call method "resolve" on an undefined value at /usr/local/oracle/perl/5.8.7/lib/DBIx/Class/Row.pm line 720. When I reverted to Version 0.07002 of DBIx-Class, I got the following error message: DBD::ODBC::st execute failed: [unixODBC][TimesTen][TimesTen 7.0.1.0.0 ODBC Driver][TimesTen]TT0907: Unique constraint (TTUNIQUE_34) violated at Rowid <0x018d19ac> -- file "ttree.c", lineno 4077, procedure "sbTtInsert" (SQL-23000)(DBD: st_execute/SQLExecute err=-1) at /usr/local/perl/5.8.7/lib/DBIx/Class/Storage/DBI.pm line 771. DBIx::Class::PK::Auto::insert(): Error executing 'INSERT INTO users (email, id) VALUES (?, ?)': [unixODBC][TimesTen][TimesTen 7.0.1.0.0 ODBC Driver][TimesTen]TT0907: Unique constraint (TTUNIQUE_34) violated at Rowid <0x018d19ac> -- file "ttree.c", lineno 4077, procedure "sbTtInsert" (SQL-23000)(DBD: st_execute/SQLExecute err=-1) at ../Local/User.pm line 298 Issue found in DBIx-Class version: 0.08010 Perl version: 5.8.7 Operating system: Linux, Red Hat Enterprise Linux AS release 3, 2.4.21-37.0.0.4.ELhugemem, i686 I found this issue with DBIx 0.08008 and reported the same but didn't get any response. Could someone provide a solution to this issue? Thanks
Nobody else has seen this behaviour with any of the 08xxx series so it's almost certainly an issue with your setup - since you don't provide a test script I've no way of trying to reproduce it. Therefore I'm rejecting the ticket - this is a support question, not a bug. Please subscribe to dbix-class@lists.scsys.co.uk and ask for help there.