Martin,
I didn't think that I ever simply substituted " for ' (since it was an issue
before and I couldn't remember what it was). However, what recently
happened was that someone was trying to insert something like:
insert into foo (DATECOL) VALUES ('01-JAN-1987 00:00:00')
and DBD::ODBC was turning that into:
insert into foo (DATECOL) VALUES ('01-JAN-1987 00??')
That's very bad...so, I added the ability to use ' and " for quoting.
Can you give me an example of why this is bad?
Thanks,
Jeff
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of [EMAIL PROTECTED]
> Sent: Monday, February 04, 2002 7:18 AM
> To: [EMAIL PROTECTED]
> Subject: Quoted Identiers - problem in DBD::ODBC 0.32
>
>
> I installed DBD::ODBC 0.32 on a machine a few weeks ago and unnotticed by
> myself (while a colleague was away on holiday) some of his cron
> jobs using Perl
> and DBD::ODBC were failing. These used to work. It appears it was
> the change in
> dbd_preparse() to use " as the quote chr instead of '. I notice
> that DBD::ODBC
> 0.33_01 test release has the ' back again but in addition to ".
>
> Can this not be a call to SQLGetInfo for SQL_IDENTIFIER_QUOTE
> which is getinfo
> number 29?
>
> Hopefully, this would then work for any identifier quote chr.
>
> Martin
> --
> Martin J. Evans
> Easysoft Ltd, UK
> Development
>
>
