Age | Commit message (Collapse) | Author | Files | Lines |
|
Fix the json1 extension so that it does not recognize ASCII form-feed as a whitespace character, in order to comply with RFC-7159.
Add a few #ifdef and build script changes to address compilation issues that appeared after the 3.9.0 release.
|
|
|
|
Policy Changes:
* The version numbering conventions for SQLite are revised to use the emerging standard of semantic versioning.
New Features And Enhancements:
* Added the json1 extension module in the source tree, and in the amalgamation. Enable support using the SQLITE_ENABLE_JSON1 compile-time option.
* Added Full Text Search version 5 (FTS5) to the amalgamation, enabled using SQLITE_ENABLE_FTS5. FTS5 will be considered "experimental" (subject to incompatible changes) for at least one more release cycle.
* The CREATE VIEW statement now accepts an optional list of column names following the view name.
* Added support for indexes on expressions.
* Added support for table-valued functions in the FROM clause of a SELECT statement.
* Added support for eponymous virtual tables.
* A VIEW may now reference undefined tables and functions when initially created. Missing tables and functions are reported when the VIEW is used in a query.
* Added the sqlite3_value_subtype() and sqlite3_result_subtype() interfaced (used by the json1 extension).
* The query planner is now able to use partial indexes that contain AND-connected terms in the WHERE clause.
* The sqlite3_analyzer.exe utility is updated to report the depth of each btree and to show the average fanout for indexes and WITHOUT ROWID tables.
* Enhanced the dbstat virtual table so that it can be used as a table-valued function where the argument is the schema to be analyzed.
Other changes:
* The sqlite3_memory_alarm() interface, which has been deprecated and undocumented for 8 years, is changed into a no-op.
Important fixes:
* Fixed a critical bug in the SQLite Encryption Extension that could cause the database to become unreadable and unrecoverable if a VACUUM command changed the size of the encryption nonce.
* Added a memory barrier in the implementation of sqlite3_initialize() to help ensure that it is thread-safe.
* Fix the OR optimization so that it always ignores subplans that do not use an index.
* Do not apply the WHERE-clause pushdown optimization on terms that originate in the ON or USING clause of a LEFT JOIN.
|
|
Adapt some packages so they build with that.
Bump their PKGREVISIONs.
|
|
|
|
|
|
=== 1.3.11 / 2015-10-10
* Enhancements:
* Windows: build against SQLite 3.8.11.1
* Internal:
* Use rake-compiler-dock to build Windows binaries. Pull #159 [larskanis]
* Expand Ruby versions being tested for Travis and AppVeyor
|
|
|
|
|
|
MySQLTuner is a script written in Perl that will assist you with your MySQL
configuration and make recommendations for increased performance and
stability.
|
|
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
|
|
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
|
|
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
|
|
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
|
|
|
|
Bugs fixed
- fixed a bug with the Cython speedups not being included
in package.
- documented how to create models with no primary key.
- allow bare INSERT statements.
- regarding foreign key / one-to-one relationships.
- allow ArrayField to accept tuples in addition to lists.
- fix regarding unsaved relations.
- refactored QueryResultWrapper to allow multiple independent
iterations over the same underlying result cache.
- fix bug with multiple joins to same table + eager loading.
- fix bug when connection fails while using an execution context.
- use correct column names with non-standard django foreign keys.
- return datetime.time instead of timedelta for MySQL time fields.
- fixed SQLite migrator regular expressions. Thanks @sroebert.
New features
- added support for RETURNING clauses. Update, Insert and Delete
queries can now be called with RETURNING to retrieve the rows
that were affected.
- added web request hook docs.
- allowed arbitrary model attributes and methods to be serialized
by model_to_dict(). Docs.
- allow model_to_dict() to introspect query for which fields
to serialize.
- Added backend-agnostic truncate_date() implementation.
- Added a FixedCharField which uses column type CHAR.
- Added support for arbitrary PRAGMA statements to be run on new
SQLite connections. Docs.
- Removed berkeley_build.sh script. See instructions on my blog
instead.
|
|
Add missing DEPENDS
Upstream changes:
version 0.2102 at 2015-03-29 09:46:45 +0000
-------------------------------------------
Change: 96eacfc5c44a2ac4c5f6ae5c4e8202c1e9f7c059
Author: Naveed Massjouni <naveed@vt.edu>
Date : 2015-03-29 05:44:09 +0000
this plugin is now a thin wrapper around DBICx::Sugar
I created DBICx::Sugar to factor out the code duplication between
Dancer::Plugin::DBIC and Dancer2::Plugin::DBIC. Now this plugin is
just a thin wrapper around DBICx::Sugar.
-------------------------------------------
version 0.2101 at 2015-02-14 02:52:24 +0000
-------------------------------------------
Change: b4b29aa82925bc53370ae15aa66e897085c31db5
Author: Naveed Massjouni <naveed@vt.edu>
Date : 2015-02-13 21:52:24 +0000
updated SQL::Translator version requirement to fix cpantesters
failures
Change: 2ee1a4bfad6362fad5907dfe85fb8d866835cef6
Author: Naveed Massjouni <naveedm9@gmail.com>
Date : 2015-01-12 01:16:15 +0000
Merge pull request #17 from monsieurp/test-code-refactoring
Test code refactoring
Change: c2b09c695a711a336e753771926c01d4a53a4c31
Author: Patrice Clement <monsieurp@gentoo.org>
Date : 2015-01-11 19:48:35 +0000
get rid of eval {} and make use of Test::Requires instead
Change: 9270cfe02c06f1de469d6e19171c3e8d1ecb2f47
Author: Patrice Clement <monsieurp@gentoo.org>
Date : 2015-01-10 20:32:36 +0000
test code refactoring and import tyding
|
|
|
|
Just some syntax sugar for your DBIx::Class applications. This was originally
created to remove code duplication between Dancer::Plugin::DBIC and
Dancer2::Plugin::DBIC.
|
|
|
|
Use Github for distfiles. Simplify build/install fixes. Readability.
LMDB 0.9.16 Release (2015/08/14)
- Fix cursor EOF bug (ITS#8190)
- Fix handling of subDB records (ITS#8181)
- Fix mdb_midl_shrink() usage (ITS#8200)
LMDB 0.9.15 Release (2015/06/19)
- Fix txn init (ITS#7961,#7987)
- Fix MDB_PREV_DUP (ITS#7955,#7671)
- Fix compact of empty env (ITS#7956)
- Fix mdb_copy file mode
- Fix mdb_env_close() after failed mdb_env_open()
- Fix mdb_rebalance collapsing root (ITS#8062)
- Fix mdb_load with large values (ITS#8066)
- Fix to retry writes on EINTR (ITS#8106)
- Fix mdb_cursor_del on empty DB (ITS#8109)
- Fix MDB_INTEGERDUP key compare (ITS#8117)
- Fix error handling (ITS#7959,#8157,etc.)
- Fix race conditions (ITS#7969,7970)
- Added workaround for fdatasync bug in ext3fs
- Don't use -fPIC for static lib
- Update .gitignore (ITS#7952,#7953)
- Cleanup for "make test" (ITS#7841), "make clean", mtest*.c
- Misc. Android/Windows cleanup
- Fix MDB_APPEND doc
- Fix MDB_MAXKEYSIZE doc (ITS#8156)
- Fix mdb_cursor_put,mdb_cursor_del EACCES description
- Fix mdb_env_sync(MDB_RDONLY env) doc (ITS#8021)
- Clarify MDB_WRITEMAP doc (ITS#8021)
- Clarify mdb_env_open doc
- Clarify mdb_dbi_open doc
|
|
|
|
=== 4.27.0 (2015-10-01)
* Don't stub Sequel.synchronize on MRI (YorickPeterse) (#1083)
* Make bin/sequel warn if given arguments that it doesn't use (jeremyevans)
* Fix the order of referenced composite keys returned by Database#foreign_key_list on PostgreSQL (jeremyevans) (#1081)
* Recognize another disconnect error in the jdbc/postgresql adapter (jeremyevans)
* In the active model plugin, make Model#persisted? return false if the transaction used for creation is rolled back (jeremyevans) (#1076)
* Use primary_key :keep_order option in the schema dumper if the auto incrementing column is not the first column in the table (jeremyevans)
* Set :auto_increment option correctly in the schema parser when the auto incrementing column is not the first column in the table (jeremyevans)
* Support :keep_order option to primary_key in schema generator, to not automatically make the primary key the first column (jeremyevans)
* Add new jsonb/json functions and operators supported in PostgreSQL 9.5+ (jeremyevans)
* Add before_after_save plugin, for refreshing created objects and resetting modified flag before calling after_create/update/save hooks (jeremyevans)
* Add Dataset#single_record! and #single_value! which don't require cloning the receiver (jeremyevans)
* Dataset#with_sql_single_value now works correctly for model datasets (jeremyevans)
* Optimize Dataset#single_value and #with_sql_single_value to not create an unnecessary array (jeremyevans)
* Make postgres adapter work with postgres-pr 0.7.0 (jeremyevans) (#1074)
|
|
0.4.1
0.4.0
@sodabrew sodabrew released this 26 days ago · 54 commits to master since this
release
New Features
* Support for Prepared Statements!
* Add connection option :sslverify
* Use mariadb_config for MariaDB builds
Bugfixes
* Fix Mysql2::Result#count always returns 0 when using stored procedures and
MULTI_STATEMENTS
Changes
* Prevent Timeout::timeout from interrupting query execution
* Use Ruby's String#encode to remove unrecognized characters from error messages
* Convert specs to RSpec 3 expect sytnax
* Refactored the Travis CI test scripts
* Misc cleanups with Rubocop
* Stricter CFLAGS
0.3.20
@sodabrew sodabrew released this on 25 Aug · 205 commits to master since this
release
Bugfixes
* Check if O_CLOEXEC is defined before using it in open()
* Fix an infinite loop while searching for libmysqlclient when mysql_config is
not found
Changes
* Call RakeCompilerDock.sh twice, once for 32-bit and once for 64-bit, when
building Windows binary gems
0.3.19
@sodabrew sodabrew released this on 30 Jul · 205 commits to master since this
release
New Features
* Mysql2::Client#info class method for easier debugging, and both the class
and instance method return US_ASCII output rather than using the connection
encoding.
* When streaming results, continue result.count across calls to result.each
Bugfixes
* Search for mariadb_config on compile
* Update to Connector/C 6.1.6 in the Windows builds
* Fix Mysql2::Client#escape to set the encoding even if the string was not
modified
* Fix LICENSE filename in gem file list
* Make the result.count return type consistent and match the source type
Changes
* Rename macro GetMysql2Result to GET_RESULT
* Convert StringValuePtr to either RSTRING_PTR or StringValueCStr
* Fix unused variable warning on Windows in rb_mysql_client_socket
* Add Ruby 2.2 to the AppVeyor matrix
* Test default client flag equality instead of bitwise truthiness
* Add rake-compiler-dock for building Windows binary gems
* Friendly ext build error <3
* Process :stream option in rb_mysql_result_to_obj once instead of
rb_mysql_result_each for each call to each
* Tests for streaming and stored procedures with multiple result sets
|
|
Version 3.5.3 Released October 1, 2015 (git commit 62ddf200106467ce9ad31d85715a4cdf63e8be14)
- Minor fix in the test file t/03dbmethod.t
|
|
* Connector/Python is now compatible with Django 1.8.
* When using the C Extension with raise_on_warnings=True, errors were not thrown as exceptions when an executed statement produced an error, and it was not possible to reuse the cursor if the statement produced a result set.
* When using the C Extension, character decoding of identifiers (database, table, column names) in result sets could fail.
* When using the C Extension with the auth_plugin option, connect() calls failed.
* In connections for which consume_results=True, callproc() could hang.
* Connections failed if the password began or ended with spaces because they were being stripped before the connection attempt.
* Connection failure occurred for accounts authenticated with the sha256_password authentication plugin that had a blank password.
* The Connector/Python C Extension could exit when fetching a result set containing many NULL values.
* Connector/Python failed to complete the connection handshake with MySQL Server 5.5.8.
|
|
* InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems.
* yaSSL was upgraded to version 2.3.8.
* RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed.
* InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset.
* InnoDB: Memory allocation sanity checks were added to the memcached code.
* InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word.
* InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.
* InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied.
* InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format.
* Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected.
* Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly
* Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE.
* Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert.
* Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
|
|
* yaSSL was upgraded to version 2.3.8.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.
* Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected.
* Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE.
* Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit.
* mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.)
* An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback.
* Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup.
* For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition.
* DELETE could check privileges for the wrong database when table aliases were used.
* Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit.
* MySQL sometimes produced no warning when it was unable to interpret a character in a given character set.
* For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit.
* Execution of certain BINLOG statements while temporary tables were open by HANDLER statements could cause a server exit.
|
|
shared-mime-info 1.5 (2015-09-15)
* Fix compilation with glib < 2.26
* Update DTD
Mime-type changes:
* Add more globs to console ROM files
* Use "folder" generic-icon for inode/directory
* Bump priority for ISO images glob matching to work
around confusion around Wii image files
* Add application/owl+xml
* Add text/turtle
* Use IANA registered image/vnd.zbrush.pcx for PCX
* Add text/rust for Rust source code
* Add application/ld+json as subclass of application/json
* Add text/csv-schema
* Add application/vnd.coffeescript
* Make application/vnd.apple.mpegurl a subclass of text/plain
* Make application/sdp a subclass of text/plain
* Add application/jrd+json as subclass of application/json
* Add MTM, MED, 699 and Ultratracker magic for application/x-mod
* Add Meson build definitions
* Match newer versions of XCF files
* Use IANA registered type for PKCS#12
* Add application/x-doom-wad
* Add Amiga disk image
* Rename "Dreamcast ROM" to "Dreamcast GD-ROM"
* Add application/x-wii-wad
* Add magic and tests to application/x-gameboy-rom
* Add application/x-saturn-rom
* Fix application/x-genesis-rom translation rules
* Split up multi-page DjVu into its own mime-type
|
|
Version 3.5.2 Released September 29, 2015 (git commit be8026c9160c4a29580a97dab57cb595c5448949)
- Fix enum value ordering on Postgres servers 9.1 and greater
[Dagfinn Ilmari Mannsåker]
- Return bigint values as plain integer values when they fit
[Dagfinn Ilmari Mannsåker]
- Fix typo in sprintf for get_info() SQL_DATA_SOURCE_NAME
[Craig A. James]
(CPAN bug #106604)
- Set the repository in META.yml to github
|
|
1.7.0 (2015-09-21)
- elasticsearch 2.0 compatibility
- thrift now deprecated, to be remoeved in future version
- make sure urllib3 always uses keep-alive
|
|
|
|
Avoid using rubyforge.org since it stopped most of services.
|
|
|
|
Avoid using rubyforge.org since it stopped most of services.
|
|
|
|
|
|
|
|
After the recent logjam attack, longer DH parameter size have been advised.
Unfortunately, this comes with a high computational cost. ECDH is a good
alternative to acheive forward secrecy with lower CPU Loads.
This patch is a backport from upstream ECDH umplementation. ECDH is
enabled by speciying a curve name through the TLSECName directive.
Valid curve names can be obtaines by openssl ecparam -list_curves
Advised usage for a forward-secrecy only setup wiht only ECDH:
TLSCipherSuite EECDH:!RC4:!SHA:!MD5:!DES:!aNULL:!eNULL
TLSECName prime256v1
If backward compatibility with older clients is required:
TLSCipherSuite EECDH:HIGH:!RC4:!SHA:!MD5:!DES:!aNULL:!eNULL
TLSECName prime256v1
Backward compatible flavor with more forward secrecy, at
the expense of using costly DH. dh2048.pem is obtained using openssl
dhparam 2048 > /etc/openssl/certs/dh2048.pem
TLSCipherSuite EECDH:EDH:HIGH:!RC4:!SHA:!MD5:!DES:!aNULL:!eNULL
TLSDHParamFile /etc/openssl/certs/dh2048.pem
TLSECName prime256v1
|
|
A 'salvage' (db_dump -r) no longer hangs on a corrupt database which contains a loop in an overflow item's chain of pages.
Remove +u1 compiler flag from the HP-UX build and fixed related alignment issue.
Fixed DB_RUNRECOVERY errors caused by pthreads-based mutexes.
Allow the failchk process to call __env_refresh when necessary.
DB->open() now detects invalid pagesizes sooner, avoiding a potential floating point exception when a purported database file has a pagesize of 0. Added a pre-verify step to the db_dump utility.
Fixed a bug that can cause DBcursor->get to return incorrect data when DB_GET_BOTH_RANGE flag is used.
Added support for Java 8.
Aborting a transaction no longer panics if a deadlock error occurs while freeing up the transaction's cursors.
Fixed a crash which could occur when multiple BDB SQL processes repeatedly open a database file.
Fixed a bug where db_printlog improperly handled a "No such file or directory" error condition.
Fixed a bug that could cause a master crash in the following cases: an unencrypted client attempts to join an encrypted replication group, or an encrypted client attempts to join an unencrypted replication group.
Fixed a bug that can cause a crash when DB_ENV->memp_stat() is called.
Added support for arm64.
Reduced the minimum hash table size.
Fixed a bug where file names were not displayed correctly when a file failed to open during backup.
Enabled cross compiling the JDBC driver.
Fixed a crash when writing to a SQL BLOB while txn_bulk is enabled.
DB->open() now detects invalid bt_minkey better, avoiding a potential floating point excetpion.
Removed EnvironmentConfig.setTxnNotDurable() and Environment.getTxnNotDurable() from the Java API. This flag cannot be set on environments.
|
|
|
|
* 0.7.0 *
* Refactor build of FreeTDS & Iconv recipes. Add OpenSSL. Merged #207.
* Ensure zero terminated strings, where C-str pointers are expected. Use StringValueCStr() Fixes #208.
* Revert 999fa571 so timeouts do not kill the client. Fixes #179.
* Remove `sspi_w_kerberos.diff` patch. Not needed anymore.
* Tested again on Azure. Added notes to README on recommended settings.
* Replace `rb_thread_blocking_region` (removed in Ruby 2.2.0) w/`rb_thread_call_without_gvl`. Fixes #182.
* Remove 30 char password warning. Fixes #172.
* Remove Ruby 1.8.6 support. We always use Time vs edge case DateTime.
|
|
=== 4.26.0 (2015-09-01)
* Make Dataset#== not consider frozen status in determining equality (jeremyevans)
* Support :if_exists option to drop_column on PostgreSQL (jeremyevans)
* Add Dataset#grouping_sets to support GROUP BY GROUPING SETS on PostgreSQL 9.5+, MSSQL 2008+, Oracle, DB2, and SQLAnywhere (jeremyevans)
* Fix handling of Class.new(ModelClass){set_dataset :table} on ruby 1.8 (jeremyevans)
* Use range function constructors instead of casts for known range types in pg_range (jeremyevans) (#1066)
* Make class_table_inheritance plugin work without sti_key (jeremyevans)
* Detect additional disconnect errors when using the tinytds adapter (jeremyevans)
* Make offset emulation without order but with explicit selection handle ambiguous column names (jeremyevans)
* Allow preparing already prepared statements when emulating limits and/or offsets (jeremyevans)
* Have Sequel::NoMatchingRow exceptions record the dataset related to the exception (pedro, jeremyevans) (#1060)
|
|
== v0.18.3 [2015-09-03] Michael Granger <ged@FaerieMUD.org>
Enhancements:
- Use rake-compiler-dock to build windows gems easily.
- Add CI-tests on appveyor and fix test cases accordingly.
Bugfixes:
- Fix data type resulting in wrong base64 encoding.
- Change instance_of checks to kind_of for subclassing. #220
- TextDecoder::Date returns an actual Ruby Date instead of a Time
(thanks to Thomas Ramfjord)
|
|
New: Support Literal IPv6 Addresses in the Database Connection URL. Ref. RFC2732
New: Honour timezone information if provided with date-time column values in Result Sets
Fixed: Issue #7 Removed onstop handler
Fixed: #8 Do not remove trailing SQL termination charachter ';' from statement
|
|
|
|
|
|
|
|
settings of INSTALL_UNSTRIPPED=yes for Darwin in individual packages.
|
|
|