Re: can't find selectrow_hashref (reinstalled with same result)

2001-04-12 Thread Tim Bunce
> What next? Wait for DBI 1.16 and meanwhile you can listen to the Twilight Zone music :) Tim.

Re: can't find selectrow_hashref (reinstalled with same result)

2001-04-12 Thread Mark Stosberg
Tim Bunce wrote: > Check that the DBI.pm in that directory contains this group of lines: > > selectrow_arrayref=>{U =>[2,0,'$statement [, \%attr [, @bind_params ] ]'] }, > selectrow_hashref=>{ U =>[2,0,'$statement [, \%attr [, @bind_params ] ]'] }, > selectall_arrayref=>{U =>[2,0,'$stateme

Re: can't find selectrow_hashref

2001-04-12 Thread Alessio Bragadini
"Brett W. McCoy" wrote: > Actually, for PostgreSQL, it is a valid statement -- CURRENT_DATE is a > global variable that always holds the current date. This SQL statement > should return a single row with 4-11-2001 Maybe the driver gets confused because it's not a column name? Try 'SELECT curre

Re: can't find selectrow_hashref

2001-04-12 Thread Tim Bunce
On Wed, Apr 11, 2001 at 08:43:21PM -0500, Mark Stosberg wrote: > Tim Bunce wrote: > > > > On Wed, Apr 11, 2001 at 05:42:03PM -0500, Mark Stosberg wrote: > > > Tim Bunce wrote: > > > > > > > > I suspect you're not really using the version you think you are. > > > > Add warn $DBI::VERSON to the cod

Re: can't find selectrow_hashref

2001-04-11 Thread Mark Stosberg
Tim Bunce wrote: > > On Wed, Apr 11, 2001 at 05:42:03PM -0500, Mark Stosberg wrote: > > Tim Bunce wrote: > > > > > > I suspect you're not really using the version you think you are. > > > Add warn $DBI::VERSON to the code. > > > > I suspected that, too. I verified that it's 1.15. (I ran it in the

Re: can't find selectrow_hashref

2001-04-11 Thread Tim Bunce
I suspect you're not really using the version you think you are. Add warn $DBI::VERSON to the code. Tim. On Wed, Apr 11, 2001 at 04:37:38PM -0500, Mark Stosberg wrote: > > Hello, > > I'm now using and enjoying the new features of DBI 1.15 (Thanks > everyone!). I have an odd issue with the ne

Re: can't find selectrow_hashref

2001-04-11 Thread Mark Stosberg
"Brett W. McCoy" wrote: > > On Wed, 11 Apr 2001, Baxter, Lincoln wrote: > > > What are you selecting from? I do not think your select is valid SQL. > > Actually, for PostgreSQL, it is a valid statement -- CURRENT_DATE is a > global variable that always holds the current date. This SQL stateme

RE: can't find selectrow_hashref

2001-04-11 Thread Brett W. McCoy
gt; Subject: can't find selectrow_hashref > > > > Hello, > > I'm now using and enjoying the new features of DBI 1.15 (Thanks > everyone!). I have an odd issue with the new method selectrow_hashref. > > When I to use it, I get the error: > test.cgi: Can&#

Re: can't find selectrow_hashref

2001-04-11 Thread Luke Crawford
TED]] > Sent: Wednesday, April 11, 2001 5:38 PM > To: > Subject: can't find selectrow_hashref > > > > Hello, > > I'm now using and enjoying the new features of DBI 1.15 (Thanks > everyone!). I have an odd issue with the new method selectrow_hashref. >

RE: can't find selectrow_hashref

2001-04-11 Thread Baxter, Lincoln
What are you selecting from? I do not think your select is valid SQL. -Original Message- From: Mark Stosberg [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 5:38 PM To: [EMAIL PROTECTED] Subject: can't find selectrow_hashref Hello, I'm now using and enjoyi

can't find selectrow_hashref

2001-04-11 Thread Mark Stosberg
Hello, I'm now using and enjoying the new features of DBI 1.15 (Thanks everyone!). I have an odd issue with the new method selectrow_hashref. When I to use it, I get the error: test.cgi: Can't locate object method "selectrow_hashref" via package "DBI ::db" at test.cgi line 32, I've verifed