On Monday, December 10, 2001, at 11:29 AM, Jeff Zucker wrote:
> It's still not clear to me exactly what you're expecting SQL::Statment
> to do, but if it's a simple as identifying the command, my newer
> version
> (still in development) can allow you to bypass the error message you're
> getting
On Monday, December 10, 2001, at 10:30 AM, Wilson, Doug wrote:
>
>> From: Terrence Brannon [mailto:[EMAIL PROTECTED]]
>>
>> On Monday, December 10, 2001, at 09:16 AM, Jeff Zucker wrote:
>>
>>> Terrence Brannon wrote:
The following SQL is not parseable by SQL::Statement:
INSER
Terrence Brannon wrote:
>
>
> sub test {
> ...
> my $parse = parse_sql $sql;## calls SQL::Statement
> ...
> return unless ($parse->{command} =~ /select/i);
It's still not clear to me exactly what you're expecting SQL::Statment
to do, but if it's a simple as identifying t
> From: Terrence Brannon [mailto:[EMAIL PROTECTED]]
>
> On Monday, December 10, 2001, at 09:16 AM, Jeff Zucker wrote:
>
> > Terrence Brannon wrote:
> >>
> >> The following SQL is not parseable by SQL::Statement:
> >>
> >> INSERT
> >>INTO thot_log (thot_fk,thot_type_fk,thot_temporality_fk,
On Monday, December 10, 2001, at 09:16 AM, Jeff Zucker wrote:
> Terrence Brannon wrote:
>>
>> The following SQL is not parseable by SQL::Statement:
>>
>> INSERT
>>INTO thot_log (thot_fk,thot_type_fk,thot_temporality_fk,date)
>>VALUES (?,?,?,CURRENT_TIMESTAMP)
>>
>> the error msg is :
>
Terrence Brannon wrote:
>
> The following SQL is not parseable by SQL::Statement:
>
> INSERT
>INTO thot_log (thot_fk,thot_type_fk,thot_temporality_fk,date)
>VALUES (?,?,?,CURRENT_TIMESTAMP)
>
> the error msg is :
>
> Parse error near CURRENT_TIMESTAMP)
What is your aim here? If you
The following SQL is not parseable by SQL::Statement:
INSERT
INTO thot_log (thot_fk,thot_type_fk,thot_temporality_fk,date)
VALUES (?,?,?,CURRENT_TIMESTAMP)
the error msg is :
Parse error near CURRENT_TIMESTAMP)
Also, this module is listed under Jochen Wiedman, but I was under
the im
