From: Caleb Epstein (caleb.epstein_at_[hidden])
Date: 2005-08-18 09:12:09
On 8/18/05, Brock Peabody <brock.peabody_at_[hidden]> wrote:
> We could make abstract_row_set::get return an optional<field> instead of
> a field. Then row::get_field could return an optional as well.
> I'd suggest that row::get, however, continue its current behavior which
> is to return a default constructed value in the presence of null fields.
I think the ability to detect NULL values for columns is a pretty
important one in any database interface. Boost.Optional sounds like
the perfect solution from a design perspective, but might hurt
performance-wise. What if there were a method like bool row::is_null
(unsigned int index)?
-- Caleb Epstein caleb dot epstein at gmail dot com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk