Happy Merry Christmas and New Year ;)
I've checked more carefully Oracle's Date and Time implementation and found small bug - incorrect year and month was inserted, also format string was not correct for result retrieving. It is fixed and working propertly ;)
So, the question is: should I put those changes to branch Libzdb 3.0 beta or not?
Good luck, Volodymyr!
On Sunday, January 5, 2014 7:23 AM, Jan-Henrik Haukeland hauk@tildeslash.com wrote:
Happy new year!
We been working on a new libzdb 3.0 release which include some new useful features. Most notable support for Date, Time and timestamp.
This release includes a lot of changes so we wanted to release this as a beta version/release candidate first. If you can, please help us test. If you find a problem, please use the issue tracker at https://github.com/tildeslash/libzdb/issues
Download: http://www.tildeslash.com/libzdb/dist/libzdb-3.0b.tar.gz MD5 checksum: 6c0334d8132723d8a58414d4b208690e Developer version: https://github.com/tildeslash/libzdb/releases
Changes in this release: ------------------------
* New: Methods for retrieving Date, Time, DateTime and TimeStamp column values from a ResultSet. PreparedStatement_setTimestamp for setting Unix timestamp.
* New: ResultSet_isnull, can be used to explicit test if a column value in a Result Set is SQL null. A Result Set already returns the NULL pointer for string and blob types and 0 for primitive data types, but to differ between SQL null and the value NULL or 0, this method can be used.
* New: PreparedStatement_getParameterCount, Returns the number of parameters in a prepared statement
* New: It is now a checked runtime error for the url parameter given in ConnectionPool_new() to be NULL.
* New: No longer require flex installed as the generated file is part of the dist.
* Fixes: Oracle: Fixed a memory corruption in OracleResultSet https://github.com/tildeslash/libzdb/issues/4
Best regards -- Jan-Henrik Haukeland
-- To unsubscribe: http://www.tildeslash.com/mailman/listinfo/libzdb-general