Age | Commit message (Collapse) | Author | |
---|---|---|---|
2010-04-01 | OTP-8511 Timestamps in ODBC | Ingela Anderton Andin | |
Now supports SQL_TYPE_TIMESTAMP on the format {{YY, MM, DD}, {HH, MM, SS}}. Thanks to Juhani Ränkimies. | |||
2010-03-09 | OTP-7452 Support for SQL_WCHAR, SQL_WVARCHAR and strings as binaries | Ingela Anderton Andin | |
ODBC now handles the types SQL_WCHAR and SQL_WVARCHAR. ODBC also has a new connection option to return all strings as binaries and also expect strings to be binaries in the param_query function. This provides some but not a full unicode support. | |||
2010-02-16 | Merge branch 'kr/odbc-netinet' into ccase/r13b04_dev | Erlang/OTP | |
* kr/odbc-netinet: Fix ODBC compilation error on FreeBSD by adding netinet/in.h to #include macros OTP-8444 The odbc application can now be compiled on FreeBSD. (Thanks to Kenji Rikitake.) | |||
2010-02-10 | Fix ODBC compilation error on FreeBSD by adding netinet/in.h to #include macros | Kenji Rikitake | |
This fix modifies lib/odbc/c_src_odbcserver.c This has been tested on FreeBSD port, and will not affect Linux. | |||
2010-02-08 | Merge branch 'po/odbc-update-delete-no-rows' into ccase/r13b04_dev | Erlang/OTP | |
* po/odbc-update-delete-no-rows: SQL_NO_DATA and SQLSTATE 00000 indicate success for updates/deletes that affect no rows | |||
2009-12-03 | SQL_NO_DATA and SQLSTATE 00000 indicate success for updates/deletes that ↵ | Paul Oliver | |
affect no rows I noticed the following when no rows were updated for an update statement: 4> odbc:param_query(Ref, "update tbadger set status = ? where badger_id = ?", [{{sql_varchar,1},["R"]}, {sql_integer, [61111]}]). {error,"No SQL-driver information available."} 5> odbc:param_query(Ref, "update tbadger set status = ? where badger_id = ?", [{{sql_varchar,1},["R"]}, {sql_integer, [61]}]). {updated,1} The attached patch, which requires the ODBC patch from Andrew Thompson, should fix it: 3> odbc:param_query(Ref, "update tbadger set status = ? where badger_id = ?", [{{sql_varchar,1},["R"]}, {sql_integer, [61111]}]). {updated,0} 4> I've followed the advice given on MSDN (http://msdn.microsoft.com/en-us/library/ms715424%28VS.85%29.aspx) and checked for SQL_NO_DATA combined with SQLSTATE 000000 | |||
2009-11-20 | The R13B03 release.OTP_R13B03 | Erlang/OTP | |