RE: TEMP column created via set_sql and MySQL DATE_FORMAT function returns 0 in Class::DBI but valid data from command-line

[prev] [thread] [next] [Date index for 2005/02/15]

From: Perrin Harkins
Subject: RE: TEMP column created via set_sql and MySQL DATE_FORMAT function returns 0 in Class::DBI but valid data from command-line
Date: 23:20 on 15 Feb 2005

On Tue, 2005-02-15 at 15:05 -0800, Terrence Brannon wrote:
> 1/ Something needs to be documented in the "DEFINING SQL STATEMENTS"
> section of the docs about this. What part of Class::DBI is taking a
> string bracked with q{} and evaluating symbols prefaced with a %?

It is touched in the Ima::DBI Queries section.  The set_sql() method is
inherited from Ima::DBI and is documented there.  You're welcome to
supply a patch for the docs that makes it more explicit though.

- Perrin

TEMP column created via set_sql and MySQL DATE_FORMAT function returns 0 in Class::DBI but valid data from command-line
Terrence Brannon 22:31 on 14 Feb 2005

Re: TEMP column created via set_sql and MySQL DATE_FORMAT function returns 0 in Class::DBI but valid data from command-line
Perrin Harkins 20:13 on 15 Feb 2005

Re: TEMP column created via set_sql and MySQL DATE_FORMAT function returns 0 in Class::DBI but valid data from command-line
Tim Bunce 22:39 on 15 Feb 2005

RE: TEMP column created via set_sql and MySQL DATE_FORMAT function returns 0 in Class::DBI but valid data from command-line
Terrence Brannon 23:05 on 15 Feb 2005

RE: TEMP column created via set_sql and MySQL DATE_FORMAT function returns 0 in Class::DBI but valid data from command-line
Perrin Harkins 23:20 on 15 Feb 2005

Generated at 11:21 on 20 Feb 2005 by mariachi v0.52