SQL::Statement1.33 appearsbuggy when only parsing SQL

Vlad, the IM-perler has asked for the wisdom of the Perl Monks concerning the following question:

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::S
+tatement.pm line 121
[download]

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. Any ideas about how I can correct this behavior are greatly appreciated.

Regards, Randolph

Update Resolved- thanks

Comment on SQL::Statement1.33 appearsbuggy when only parsing SQL Download Code

Replies are listed 'Best First'.
Re: SQL::Statement1.33 appearsbuggy when only parsing SQL by bart (Canon) on Sep 05, 2012 at 20:16 UTC
What SQL? I think it would help if you just gave a real example of an SQL command that it chokes on. As it is, we can only guess.	[reply]
Re: SQL::Statement1.33 appearsbuggy when only parsing SQL by Anonymous Monk on Sep 05, 2012 at 15:03 UTC
Any ideas about how I can correct this behavior are greatly appreciated. write a test case and share with us	[reply]