Re: selectrow_hashref in DBI 1.32 doesn't always return a hashref

2003-02-16 Thread Craig Sanders
On Sat, Feb 15, 2003 at 12:56:09PM +, Tim Bunce wrote: > On Sat, Feb 15, 2003 at 11:23:13AM +1100, Craig Sanders wrote: > > so, it looks like in plain perl selectrow_hashref returns undef when the > > record doesn't exist, but in HTML::Mason it returns the scalar '1'. > > Thanks. Dig deeper. I

Re: selectrow_hashref in DBI 1.32 doesn't always return a hashref

2003-02-15 Thread Craig Sanders
On Sat, Feb 15, 2003 at 10:51:14AM +1100, Craig Sanders wrote: > On Fri, Feb 14, 2003 at 11:05:19AM +, Tim Bunce wrote: > > Can you post an example script that calls selectrow_hashref and > > demonstrates the problem? > > the application is written in HTML::Mason, so all the stuff for opening

Re: selectrow_hashref in DBI 1.32 doesn't always return a hashref

2003-02-15 Thread Craig Sanders
On Fri, Feb 14, 2003 at 11:05:19AM +, Tim Bunce wrote: > Can you post an example script that calls selectrow_hashref and > demonstrates the problem? the application is written in HTML::Mason, so all the stuff for opening the database, session management, etc is absent from this test script. (

Re: selectrow_hashref in DBI 1.32 doesn't always return a hashref

2003-02-15 Thread Tim Bunce
On Sat, Feb 15, 2003 at 11:23:13AM +1100, Craig Sanders wrote: > On Sat, Feb 15, 2003 at 10:51:14AM +1100, Craig Sanders wrote: > > On Fri, Feb 14, 2003 at 11:05:19AM +, Tim Bunce wrote: > > > Can you post an example script that calls selectrow_hashref and > > > demonstrates the problem? > > >

Re: selectrow_hashref in DBI 1.32 doesn't always return a hashref

2003-02-14 Thread Tim Bunce
Can you post an example script that calls selectrow_hashref and demonstrates the problem? Tim. On Fri, Feb 14, 2003 at 01:18:56PM +1100, Craig Sanders wrote: > this seems to have changed since i installed DBI 1.32 (i upgraded from 1.30), > and is breaking some scripts which assume that it will al

selectrow_hashref in DBI 1.32 doesn't always return a hashref

2003-02-14 Thread Craig Sanders
this seems to have changed since i installed DBI 1.32 (i upgraded from 1.30), and is breaking some scripts which assume that it will always return a hash. sometimes (when the query returns no rows), it returns the scalar "1" - attempting to use that as a hashref causes the script to die (with "str