From: Thorsten Ottosen (thorsten.ottosen_at_[hidden])
Date: 2007-03-15 04:26:57
Maciej Sobczak wrote:
> Jeff Garland wrote:
>>Well, I'll be brutally honest -- I don't think I would go that
>>direction. We didn't pick a database project last year because a
>>majority of the mentors agreed that the 'dsl-based' approach was more of
>>a toy than reality. The main reason for this is that in 'real-world'
>>applications queries are often dynamic and must be built at run-time.
> The other reason is that in 'real-world' you might want to call stored
> procedures instead of manually glued pieces of ad-hoc SQL queries, in
> which case the support in the area of query composition is probably not
> very useful anyway.
In the 'real-world' both things are used.
Choosing C++ for a projects where databases are involved is probably
rare and Java/C#/Python/Ruby is more likely. C++ doesn't exactly
boost productivity, so it has to offer something else to be a condidate.
And what can C++ offer? Type safety.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk