[Sqlrelay-discussion] RE: NULL values from queries

[Dave S. <dsu...@co...>]

Ok, so I sent the message and then I went to look though the =20
interface again to see if there was a good solution.  Well, it turns =20
out that there is a portability option in the PEAR DB stuff to switch =20=

between getting NULLs as empty strings or real NULLs and this wasn't =20
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 =20
includes the patch that I previously submitted to you with the lower =20
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 =20
> application to support SQLRelay.  I'm converting from the PEAR oci8 =20=

> (Oracle) interface.  I'm having a problem because of NULL values.  =20
> I see the default for SQLRelay is to return empty strings instead =20
> of NULLs (sqlrcur_getNullsAsEmptyStrings) and this is problematic =20
> for the code (it is expecting NULLs).  I see the function to change =20=

> 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 =20
> this function call when the cursor is created (except to modify the =20=

> 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 =20
> interface to make this configurable.
>
> Anyone have any suggestions?
>
> Thanks
> Dave

=EF=BF=BC=