Tim wrote:
> The DBI tries to follow the basic principle that it should be as
> transparent as possible. "Don't mess with the data."
<snip>
> If you don't want them to be in the data coming out of the database
> then they should have been removed on the way in.
It all started when I developed this application using Sybase's C++
IDE. It had a bug that could not handle empty Foxpro memo fields -- I
had to add a single space. This isn't a problem since rewriting it in
Perl. So now I CAN remove them going in.
> In DBI v2 you'll be able to do things like this for specific columns:
> $sth->bind_col(1, undef, { OnFetch => sub { s/\s$// } });
> and use something like this to apply to all columns of a certain type:
> $dbh->{DefaultBindTypeArgs} = {
> SQL_VARCHAR => { OnFetch => sub { s/\s$// } },
> };
V2 sounds terrific!
Thanks for your help on this!
Stephen Toney
Systems Planning
[EMAIL PROTECTED]
http://www.systemsplanning.com
