Mercurial > hg > monetdb-java
changeset 153:836c49b890ec
For public releases compile MonetDB JDBC driver code and jdbcclient program
without debug info and with optimise flag enabled.
| author | Martin van Dinther <martin.van.dinther@monetdbsolutions.com> |
|---|---|
| date | Thu, 24 Aug 2017 15:25:13 +0200 (2017-08-24) |
| parents | 352b54ff0436 |
| children | 9a026aa272bb |
| files | ChangeLog build.properties |
| diffstat | 2 files changed, 11 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog +++ b/ChangeLog @@ -1,13 +1,18 @@ # ChangeLog file for monetdb-java # This file is updated with Maddlog +* Thu Aug 24 2017 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> +- The MonetDB JDBC driver code and jdbcclient program are now compiled + without debug info and with optimise flag enabled. The new jar files are + now smaller in size. + * Thu Aug 17 2017 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Implemented ResultSet method getNCharacterStream() - In class MonetClob implemented methods getCharacterStream() and getCharacterStream(long pos, long length). Method getCharacterStream() is called by DBeaver to fetch the Clob value. It used to throw a SQLFeatureNotSupportedException with message: - "Method getCharacterStream() currently not supported" This caused + "Method getCharacterStream() currently not supported". This caused DBeaver to log the exception and show NULL as the value on screen, which is incorrect. This has been fixed.
--- a/build.properties +++ b/build.properties @@ -30,7 +30,8 @@ JDBC_DEF_PORT=50000 ## General ## -# should we compile with debugging symbols -enable_debug=true -# should we optimize the build, preferably not for debugging -enable_optimize=false +# should we compile with debugging symbols? Not for public releases +enable_debug=false + +# should we optimize the build, preferably not for debugging. Yes for public releases +enable_optimize=true