Re: INSERTing problems

2001-06-09 Thread Randal L. Schwartz
> "Dave" == Dave Newton <[EMAIL PROTECTED]> writes: Dave> Randal said: >> Placeholders are even more cool, and require less thinking. Dave> If they're supported, which they aren't under all platforms! They're supported by DBI, so it's *all* platforms. Perhaps you're thinking of the ":1"-st

RE: INSERTing problems

2001-06-09 Thread Dave Newton
Liz said: > I've not done a great deal of Perl, but with VB we always stripped the > apostrophes out before putting variables into SQL statements. I just escape them-why take them out? They do serve a purpose. Randal said: > Placeholders are even more cool, and require less thinking. If they'r

Re: INSERTing problems

2001-06-08 Thread Jeff Yoak
At 05:28 AM 6/8/01 -0700, Randal L. Schwartz wrote: > > "Jeff" == Jeff Yoak <[EMAIL PROTECTED]> writes: > >Jeff> I'm coming in on the middle of a thread here, but generally the best >Jeff> thing to do when working with databases in Perl is to us DBI, and if >Jeff> you are doing that, database

Re: INSERTing problems

2001-06-08 Thread Randal L. Schwartz
> "Jeff" == Jeff Yoak <[EMAIL PROTECTED]> writes: Jeff> I'm coming in on the middle of a thread here, but generally the best Jeff> thing to do when working with databases in Perl is to us DBI, and if Jeff> you are doing that, database handles have a method called quote() that Jeff> will ensur

Re: INSERTing problems

2001-06-08 Thread Jeff Yoak
At 09:07 AM 6/8/01 +0100, Liz Keogh wrote: >For my own personal curiosity; > >Would you have to somehow protect the apostrophe in something >like "Kelly's Trucking" before putting it into an SQL string? I'm coming in on the middle of a thread here, but generally the best thing to do when working

Re: INSERTing problems

2001-06-08 Thread Liz Keogh
For my own personal curiosity; Would you have to somehow protect the apostrophe in something like "Kelly's Trucking" before putting it into an SQL string? I've not done a great deal of Perl, but with VB we always stripped the apostrophes out before putting variables into SQL statements. Cheer

Re: INSERTing problems

2001-06-07 Thread David Labatte
It's been some time since I've done any access programming but the error your getting is consistent with using a reserved world for a table or field name. According to the below reference from Microsoft's site the world 'Full' is a indeed a reserved word in access and could be the cause of your p

RE: INSERTing problems

2001-06-07 Thread Moon, John
hn W Moon -Original Message- From: SAWMaster [mailto:[EMAIL PROTECTED]] Sent: June 07, 2001 16:20 To: [EMAIL PROTECTED] Subject: INSERTing problems Curtis Poe said: >As for your code problem, after instantiating a DBI object, try adding the following line of code: >DBI->trace

INSERTing problems

2001-06-07 Thread SAWMaster
Curtis Poe said: >As for your code problem, after instantiating a DBI object, try adding the following line of code: >DBI->trace( 2, 'errors.txt' ); >From the documentation: >DBI->trace($trace_level) >DBI->trace($trace_level, $trace_filename) >DBI trace information can be enabled for all hand