Escaping with a backslash might become a problem later. Jeff and I talked before, and not sure about his vision on this, I want SQL::Parser, which comes with SQL::Statement, to become a universal SQL::Parser and therefore possibly used by all DBDs and possibly DBI iteself, for any SQL parsing needs. It will of course have to be configurable. So a possible config can be an attribute with an escape character.
Ilya -----Original Message----- From: Simon Oliver To: Ronald J Kimball Cc: Ron Hall; [EMAIL PROTECTED] Sent: 1/11/02 8:07 AM Subject: Re: DBI::AnyData question > According to the docs Simon quoted, for DBD::AnyData Actually, it's due to SQL::Statement which is used by a number of DBD modules including DBD::AnyData and DBD::CSV > you need to escape a > single quote with a backslash, not with another single quote, as you would > for most other DBDs. Which is why it is better to use the $dbh->quote method or placeholders - they are more portable! -- Simon Oliver
