Markus Hoenicka <markus.hoeni...@mhoenicka.de> wrote:
> I've had a look at libdbi-driver's current ato*() usage. As far as I
> can see it is used only to turn raw row data into integers by
> functions which do not return values, i.e. without an easy way to
> indicate conversion errors. I haven't checked all drivers yet, but I
> see two options:
[snip]
I'm going to have to take a step back for a moment: Currently the only
thing that I have that is using libdbi is one legacy application. I'm
not saying that I won't use it in future projects, just that I have no
active projects at the moment depending on it. Therefore other users
may have more of an opinion. (I originally stepped into this conversation
to answer the "what's wrong with ato*?" question on a more theoretical
basis.)
Also, your userbase may be wary of anything that results
in an API change, at least between minor versions. Even if you can't
propagate an error, you should be able to log the problem, though.
That being said, I do not think that it is unreasonable for dbd_fetch_row
to error out if there is a problem parsing any of the result columns.
One should be able to determine (from log files, if not programatically)
the set of all problems in that case, though.
Devin
--
I'm not a complete idiot, some parts are missing.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
libdbi-users mailing list
libdbi-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libdbi-users
