Re: '?' in SQL-comments fails

2001-09-18 Thread Jonathan Leffler
Stephen Clouse wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, Sep 12, 2001 at 01:23:59AM +0200, Bart Lateur wrote: > > OK, probably a stupid question: Why do you want to have comments inside > > the SQL statements? It looks useless to me. Most databases even choke on > > the

Re: '?' in SQL-comments fails

2001-09-13 Thread Tim Bunce
On Thu, Sep 13, 2001 at 09:41:12AM +0100, Simon Oliver wrote: > > FYI, the DBI is working towards having all drivers (optionally) share > > the same (parameterized) SQL pre-parser. The preparser will support > > many whizzo features like rewriting comments from one style to another > > if the orig

Re: '?' in SQL-comments fails

2001-09-13 Thread Simon Oliver
> FYI, the DBI is working towards having all drivers (optionally) share > the same (parameterized) SQL pre-parser. The preparser will support > many whizzo features like rewriting comments from one style to another > if the original style is not supported by the database engine being used. > More

Re: '?' in SQL-comments fails

2001-09-12 Thread Michael Peppler
Stephen Clouse writes: > Pretty much every SQL server I've found groks the /* */ construct as a comment. > MySQL, Oracle, and PG handle it fine. I don't use Sybase but I know it supports > it as well, and by extension MSSQL probably does also. But I highly doubt any > of them support pla

Re: '?' in SQL-comments fails

2001-09-12 Thread Tim Bunce
On Wed, Sep 12, 2001 at 08:05:41AM -0700, Michael Peppler wrote: > Ronald J Kimball writes: > > On Wed, Sep 12, 2001 at 01:23:59AM +0200, Bart Lateur wrote: > > > On Tue, 11 Sep 2001 23:07:03 +0200, Morten Hanshaugen wrote: > > > > > > >It would be nice if '?'-characters inside comments could

Re: '?' in SQL-comments fails

2001-09-12 Thread Stephen Clouse
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Sep 12, 2001 at 01:23:59AM +0200, Bart Lateur wrote: > OK, probably a stupid question: Why do you want to have comments inside > the SQL statements? It looks useless to me. Most databases even choke on > the innocent semicolon at the end of th

Re: '?' in SQL-comments fails

2001-09-12 Thread Peter J . Holzer
On 2001-09-12 09:11:02 -0400, Ronald J Kimball wrote: > On Wed, Sep 12, 2001 at 01:23:59AM +0200, Bart Lateur wrote: > > OK, probably a stupid question: Why do you want to have comments inside > > the SQL statements? > > For the same reason you would use comments anywhere; to document the code, >

Re: '?' in SQL-comments fails

2001-09-12 Thread Michael Peppler
Ronald J Kimball writes: > On Wed, Sep 12, 2001 at 01:23:59AM +0200, Bart Lateur wrote: > > On Tue, 11 Sep 2001 23:07:03 +0200, Morten Hanshaugen wrote: > > > > >It would be nice if '?'-characters inside comments could escape being > > >counted when calculating and/or expanding the number of

Re: '?' in SQL-comments fails

2001-09-12 Thread Ronald J Kimball
On Wed, Sep 12, 2001 at 01:23:59AM +0200, Bart Lateur wrote: > On Tue, 11 Sep 2001 23:07:03 +0200, Morten Hanshaugen wrote: > > >It would be nice if '?'-characters inside comments could escape being > >counted when calculating and/or expanding the number of needed > >arguments. > > OK, probably

Re: '?' in SQL-comments fails

2001-09-11 Thread Michael Ragsdale
At 11:07 PM 9/11/01 +0200, Morten Hanshaugen wrote: >It would be nice if '?'-characters inside comments could escape being >counted when calculating and/or expanding the number of needed >arguments. >Example code: >$dbh->prepare("/*root there?*/ select user from user where user = ?"); It is not

Re: '?' in SQL-comments fails

2001-09-11 Thread Bart Lateur
On Tue, 11 Sep 2001 23:07:03 +0200, Morten Hanshaugen wrote: >I just want to let you >know that question signs ('?') inside /* ... */ comments in a >SQL-statement gives the following error message: > >DBD::mysql::st execute failed: called with 1 bind variables when 2 are needed at -e >line 1. >

'?' in SQL-comments fails

2001-09-11 Thread Morten Hanshaugen
Sorry to interrupt on you on such a tragic day. I just want to let you know that question signs ('?') inside /* ... */ comments in a SQL-statement gives the following error message: DBD::mysql::st execute failed: called with 1 bind variables when 2 are needed at -e line 1. It would be nice if '