Skip Menu |

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

Report information
The Basics
Id: 44034
Status: rejected
Priority: 0/
Queue: SQL-Statement

People
Owner: Nobody in particular
Requestors: casueps [...] hotmail.com
Cc:
AdminCc:

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



Subject: problems with mysql queries
Date: Wed, 11 Mar 2009 13:25:25 +0000
To: <bug-sql-statement [...] rt.cpan.org>
From: Toni Casueps <casueps [...] hotmail.com>
I'm trying to parse a query and I get this error: SQL ERROR: Junk after table name 'N30_naps_future' This is the code that I used: $parser = SQL::Parser->new(); my $success = $parser->parse("update N30_naps_future n, nenaptype t set match_port_userlabel = concat(n.actual_eqpt_name,'/',replace(replace(t.userlabeltype,'SLOTNUMBER',concat('%',n.card)),'PORTNUMBER',concat('%',n.port)) ) where n.actual_eqpt_netype = t.netypeid"); my %output = %{$parser->structure}; The sentence is correct because I can execute it with a MySQL client. Is this a bug in the parser? Show quoted text
_________________________________________________________________ Llévate Messenger en el móvil a todas partes ¡Conéctate! http://www.microsoft.com/spain/windowsmobile/messenger/default.mspx
ANSI SQL 2003 says about the UPDATE syntax: UPDATE [ONLY] {table_name | view_name} SET {{column_name = { ARRAY [array_val[, ...]] | DEFAULT | NULL | scalar_expression }, column_name = ... } | {ROW = row_expression} [ WHERE search_condition | WHERE CURRENT OF cursor_name] Sure, SQL::Statement doesn't support the full SQL ANSI 2003 Standard, but it doesn't implement any MySQL modifications. Maybe it comes one time?