Jeff Garland wrote:
The database compiler vendors will suddenly have to provide with their compiler to satisfy the standard requirements? Probably not... Compiler vendors won't start writing databases (except Microsoft, of course :-) ). This means that this standard interface would be directed to database vendors rather than compiler vendors. Is this the plan? That database vendors will start supplying C++ header files and lib files with a "C++ Compliant" stamp?
You raise a good point. Virtually all database vendors supply an ODBC interface -- so I would expect that this would be the primary basic 'driver interface' supplied by companies building standard libraries. However, I would expect the architecture to allow for database or standard library vendors to provide high performance native bindings for particular databases.
So we're standardizing ODBC? The committee would require compiler/std-lib vendors to supply a C++ wrapper for ODBC (without forbidding supplying additional wrappers with same interface for other databases)?