Bug #54129 for SQL-Interp: $id_match doesn’t take quoting into account

Fri Jan 29 12:41:01 2010 AWNCORP [...] cpan.org - Ticket created

# test case my ($sql, @bind) = sql_interp 'INSERT INTO `group`', \%item; # issue This doesn't produce the correct SQL statement. The reason I assume is because the mysql table name is escaped using backticks which is neccessary because it is a keyword. Un-escaping it fixes the problem but renders the statement useless as the database thinks I am using the keyword. This has been tested with SQLite and MySQL.

Fri Jan 29 13:55:20 2010 mark [...] summersault.com - Correspondence added

Subject:	Re: [rt.cpan.org #54129]
Date:	Fri, 29 Jan 2010 13:54:53 -0500
To:	bug-SQL-Interp [...] rt.cpan.org
From:	Mark Stosberg <mark [...] summersault.com>

Show quoted text

> # test case > my ($sql, @bind) = sql_interp 'INSERT INTO `group`', \%item; > > # issue > This doesn't produce the correct SQL statement. The reason I assume is > because the mysql table name is escaped using backticks which is > neccessary because it is a keyword. Un-escaping it fixes the problem but > renders the statement useless as the database thinks I am using the > keyword. This has been tested with SQLite and MySQL.

Thanks for the report. A patch and test would be welcome. Mark

Fri Jan 29 13:55:23 2010 The RT System itself - Status changed from 'new' to 'open'

Fri Mar 09 05:08:31 2018 ARISTOTLE [...] cpan.org - Subject changed from (no value) to '$id_match doesn’t take quoting into account'

Wed Apr 08 06:37:11 2020 yorhel [...] cpan.org - Correspondence added

Fixed on git: https://code.blicky.net/yorhel/SQL-Interp/commit/6acb93f4cab30c55f909bb2c5419007881a14ce3 Will make it into the next release, which I'll upload within a week or so.

Wed Apr 08 06:37:13 2020 yorhel [...] cpan.org - Status changed from 'open' to 'resolved'