On Tue, Apr 27, 2004 at 12:14:08AM +0200, H.Merijn Brand wrote:
> On Mon 26 Apr 2004 17:31, "Dean Arnold" <[EMAIL PROTECTED]> wrote:
> > > On Sat 24 Apr 2004 21:38, "Dean Arnold" <[EMAIL PROTECTED]> wrote:
> > > > $sth->{TYPE}->[0] == SQL_DECIMAL,
> > > > $sth->{PRECISION}->[0] == 10,
> > > > $sth->{SCALE}->[0] == 2 => $sth->{TYPE_STRING}->[0] =
> > > > 'DECIMAL(10,2)'
> > 1) Drivers should provide their own TYPE_STRING values, presumably in their
> > native platforms' format
> >
> > 2) For any driver that doesn't provide TYPE_STRING, but *does* provide
> > type_info_all(),
> > DBI layer would generate TYPE_STRING from the information from type_info_all(),
> > {TYPE}, {PRECISION}, {SCALE}
> >
> > 3) For drivers that provide neither TYPE_STRING nor type_info(), DBI generates
> > TYPE_STRING from 'standard' type names and {TYPE}/{PRECISION}/{SCALE}
>
> This is more clear to me, and I think it covers my request.
I'd consider a patch, with documentation and tests.
Tim.
