We have been using soci with the ODBC backend for over a year, in a big project (database related code is 20000 lines). The only problems I found were that: - long long (64-bit integers) were unsupported. That caused memory corruption in my Windows box when I read integer columns of more than 9 digits, as I was forced to insert them into 32 bit integers. I added long long support and seems fine. In 64 bits-linux there was no problem, as unsigned long is supported by the backend, and in that platform long is 64-bit, unlike Windows. - valgrind and windows pageheap report some memory errors, but they do not crash my program
I want to ask, ¿which were the reasons because ODBC was not considered stable? ¿which tasks should be performed to reinclude it in a new release? (apart from memory profiling...) ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
