On Tue, Mar 19, 2002 at 12:20:43PM +0100, Steffen Goeldner wrote:
> Tim Bunce wrote:
> >
> > On Mon, Mar 18, 2002 at 12:05:28PM +0100, Steffen Goeldner wrote:
>
> > A more realistic example would be for drivers that return empty
> > strings or NULL for the catalog portion.
>
> Currently, DBD::Oracle's table_info() method returns '' -> NULL ->
> undef for the PUBLIC pseudo-schema:
>
> , decode( t.OWNER, 'PUBLIC', '', t.OWNER ) TABLE_SCHEM
>
> Oracle's weird '' -> NULL conversion has one advantage: DBI's
> tables() method does the right thing (it omits the schema part).
> BTW: Should tables() really return something like '""."DBA_TABLES"'
> for empty schemas?
I'm not sure what you mean by empty schema.
> Unfortunately, an empty schema argument (currently) does not match
> the PUBLIC schema.
> Should I generate another predicate for that case?
What does Oracle's ODBC driver do?
> > > + However, an empty string ('') is treated as a regular search criteria
> > > + and will only match an empty value.
> >
> > Does that apply equally ato both ordinary values and search patterns?
>
> I think yes. Maybe I'm wrong, but see again
>
> <http:[EMAIL PROTECTED]/msg01045.html>
>
> for *my* interpretation of the ODBC spec. (IMO, the spec gives a very
> nebulous impression about that topic.)
[Sigh]
> Steffen
> *** DBI-1.21-orig/DBI.pm Thu Feb 07 04:15:50 2002
> --- DBI.pm Mon Mar 18 23:27:01 2002
Thanks again Steffen.
Tim.
