Skip Menu |

This queue is for tickets about the SQL-Statement CPAN distribution.

Report information
The Basics
Id: 79473
Status: resolved
Priority: 0/
Queue: SQL-Statement

People
Owner: Nobody in particular
Requestors: randolph [...] deepcloud.com.au
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 1.33
Fixed in: 1.17



Subject: Can't do parse only - buildCondition undefined method
I recently upgraded some software using SQL::Statement v 1.17 to 1.27 After fixing the obvious documented changes around the column_names struct I have come across a problem with a null buildCondition. I upgraded further to 1.33 but the problem persists Specifically,my code which only uses SQL::Statement to parse and rewrite SQL for an existing external database, returns the error: Can't call method "buildCondition" on an undefined value at.... SQL::Statement.pm line 121 When a where clause is used in the SQL. Its not possible that all DB structures will be known to the perl subsystem and my program likes to know nothing about column specifics. Works: select sum(duration) from cdr; Broken: select sum(duration) from cdr where duration >0; Platform: perl 5.8.8 Centos5.7 Intel I5 8 GRAM
And where exactly is the error in SQL::Statement? Can you demonstrate code which is expecting to work and doesn't as mentioned in the Support section of the SQL::Statement documentation?
From: randolph [...] deepcloud.com.au
Thanks for the quick response. While preparing a example program I realised that my subclass had poor instantiation. This problem only showed up with the later versions. sorry -please close. My bad.
Well, that's why the Support sections says: "[...] Report tickets should contain a detailed description of the bug or enhancement request and at least an easily verifiable way of reproducing the issue or fix. [...]" ;) I'm happy that you found a solution - not every reporter has such a clear mind.