Hey Mobi Phil, 2010/3/14 mobi phil <[email protected]>: > Hello, > > did you already think about keys under which to store some driver > (backend) related settings?
It depends, we are certainly thinking of a nice solution to support SQL dialects, especially w.r.t. different types. Do you have other uses in mind ? > and a little observation.. > 1. SqlStatement::getResult family... passing output values as pointers > are not really C++ (rather C style), or? (reference would be mabye > preffered) Perhaps that would have been better. But no point in changing it now, I think ? They are really different syntax for the same thing. > 2. Doing DB operations on constructors (SqlStatement, SqlConnection) > is maybe not the best idea, as it makes exception handling, > deallocation etc. generally difficult. What happens if a driver throws > an exception on these constructors? I believe throwing exceptions from a constructor is perfectly fine ? (http://www.parashift.com/c++-faq-lite/exceptions.html#faq-17.2) I have not checked the actual implementations of SqlStatement/SqlConnection, but they could certainly be written so that they do not leak memory when an exception occurs... Regards, koen ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
