From: Steve Hutton (shutton_at_[hidden])
Date: 2006-10-07 14:04:51
On 2006-10-06, Nicola Musatti <Nicola.Musatti_at_[hidden]> wrote:
> In my view the real problem is to decide where to stop, i.e. to decide what
> should go into Boost.SQL and what should go in other libraries, built above it.
It's an interesting point. I guess the downside of a limited interface
might be that users could end up preferring to use an enhanced version of
the library instead.
> My view is very conservative: support as much of SQL as possible, but limit the
> interface with C++ to simple types and tuples. Remember that we need to come out
> with something that is digestible not only for the C++ standardization
> committee, but possibly also for the SQL one.
I can see that ideally the API of Boost.SQL would be as close as
possible to the API of std::sql. But do you think it also might be
reasonable to have Boost.SQL potentially be a superset of std::sql?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk