Re: [Sqlrelay-discussion] RE: NULL values from queries

[David M. <dav...@fi...>]

I just applied this patch.  It's in CVS now.

Dave

On Tue, 2006-03-14 at 06:47 -0500, Dave Sugar wrote:
> Ok, so I sent the message and then I went to look though the interface
> again to see if there was a good solution.  Well, it turns out that
> there is a portability option in the PEAR DB stuff to switch between
> getting NULLs as empty strings or real NULLs and this wasn't being
> checked by the SQLRelay PEAR code.
> 
> 
> So, I have modified this and attached a patch.
> 
> 
> David - please note this is a patch against your CVS tree.  It
> includes the patch that I previously submitted to you with the lower
> case of column names.
> 
> 
> Dave Sugar
> 
> 
> Begin forwarded message:
> 
> > From: Dave Sugar <dsu...@co...>
> > Date: 14 March, 2006 5:59:53 EST
> > To: sql...@li...
> > Subject: NULL values from queries
> > 
> > 
> > I'm using the PEAR PHP interface for SQLRelay while modifying an
> > application to support SQLRelay.  I'm converting from the PEAR oci8
> > (Oracle) interface.  I'm having a problem because of NULL values.  I
> > see the default for SQLRelay is to return empty strings instead of
> > NULLs (sqlrcur_getNullsAsEmptyStrings) and this is problematic for
> > the code (it is expecting NULLs).  I see the function to change the
> > setting to that NULLs are returned (sqlrcur_getNullsAsNulls).
> > 
> > 
> > But, as I'm using the PEAR interface I don't see a way of making
> > this function call when the cursor is created (except to modify the
> > source DB/sqlrelay.php).  
> > 
> > 
> > Is there a way to modify this default value globally?
> > 
> > 
> > I don't know that there is a reasonable way to modify the PEAR
> > interface to make this configurable.  
> > 
> > 
> > Anyone have any suggestions?
> > 
> > 
> > Thanks
> > Dave
> 
> 
> 
>