Hi, I'm working with an application that uses a BIGINT (UNSIGNED) column type in a MySQL database, and uses the full (64 bit) range of the field. >From reading the SOCI documentation, it seems that BIGINT fields are truncated to 32 bit ints. Is there planned support for using 64-bit ints for the BIGINT field? If not, what would be involved (and where would I start looking) in creating support for this?
Also, this same application uses some normal INT UNSIGNED fields, but expects the full range of the 32 bit UNSIGNED type. Does SOCI correctly handle signed vs unsigned types? If not, what would be involved in making it correctly handle these? Thanks, Chris Breneman ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
