On Mon, Aug 23, 2004 at 03:53:51PM -0400, Steven Lembark wrote:
> For example "neat" (see below for perldoc) 'knows' if a string
> is numeric or char in the database.

Not quite. It knows if the perl scalar value has numeric and/or
string representations cached (the SvPOK and SvINOK flags).

> If I could get a hash keyed
> by $sth->{NAME} that had, say, DBD-specific metadata it'd help
> quite a bit on handling some error situaions. One use is returning
> a copy of the query with placeholders filled in for cut+paste
> troubleshooting;

I don't see how anything keyed by NAME could help with anything
related to placeholders.

For placeholders the ParamValues attribute exists already and
I've also previously talked about adding a ParamAttribs attribute.

> another is pretty-printing results where numeric
> sequences stored as strings need to be quoted for further use
> (i.e., /^\d+$/ is not a good enough test for quotishness when
> Perl gets all the data back as strings).

DBI::looks_like_number() would be better, for some definition of better.

> If whatever neat uses were exported -- perhaps in DBD-specific
> fashion to accomodate varying levels of metadata available in
> the different databases -- it'd sure help...

Some concrete examples would sure help me :)

Tim.

Reply via email to