summaryrefslogtreecommitdiff
path: root/databases
AgeCommit message (Collapse)AuthorFilesLines
2015-10-12Add missing py-cython bl3, fixes PLIST phasefhajny1-1/+2
2015-10-11+mysqltunerrodent1-1/+2
2015-10-11Import mysqltuner-1.6.0 as databases/mysqltuner.rodent4-0/+54
MySQLTuner is a script written in Perl that will assist you with your MySQL configuration and make recommendations for increased performance and stability.
2015-10-11Changes 9.1.19:adam4-8/+12
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.
2015-10-11Changes 9.2.14:adam4-8/+13
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.
2015-10-10Changes 9.3.10:adam4-8/+14
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.
2015-10-10Changes 9.4.5:adam5-28/+19
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.
2015-10-10Recursive revbump from textproc/icuryoon23-38/+46
2015-10-08Update databases/py-peewee to 2.6.4.fhajny3-9/+9
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.
2015-10-07Update to 0.2102wen2-7/+7
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
2015-10-07add p5-DBICx-Sugarwen1-1/+2
2015-10-07Import DBICx-Sugar-0.0001 as databases/p5-DBICx-Sugar.wen3-0/+34
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.
2015-10-07Fix building with some libedit and libreadline, including those on NetBSDadam4-18/+41
2015-10-07Update databases/lmdb to 0.9.16.fhajny3-25/+42
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
2015-10-07Needs USE_GCC_RUNTIME=yes to work with gcc??-libs packages. PKGREVISION++fhajny1-1/+4
2015-10-04Update ruby-sequel to 4.27.0.taca3-7/+10
=== 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)
2015-10-04Update ruby-mysql2 to 0.4.1.taca3-7/+27
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
2015-10-04Update to 3.5.3:wiz2-6/+6
Version 3.5.3 Released October 1, 2015 (git commit 62ddf200106467ce9ad31d85715a4cdf63e8be14) - Minor fix in the test file t/03dbmethod.t
2015-10-03Changes 2.1.3:adam3-7/+22
* 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.
2015-10-03Changes 5.6.27:adam4-33/+66
* 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.
2015-10-03Changes 5.5.46:adam4-21/+17
* 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.
2015-09-30Update to 1.5:wiz3-7/+8
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
2015-09-30Update to 3.5.2:wiz2-7/+6
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
2015-09-25Update py-elasticsearch to 1.7.0.fhajny2-6/+6
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
2015-09-25Avoid using rubyforge.org since it stopped most of services.taca1-3/+3
2015-09-25Update HOMEPAGE.taca1-2/+2
Avoid using rubyforge.org since it stopped most of services.
2015-09-25Avoid using rubyforge.org since it stopped most of services.taca7-14/+14
2015-09-25Update HOMEPAGE.taca1-2/+2
Avoid using rubyforge.org since it stopped most of services.
2015-09-21Fix build of databases/sqlrelay-nodejs by adding nodejs>4 support.fhajny2-1/+26
2015-09-17Add missing py-cython dependency, as noted by joerg.fhajny1-1/+3
2015-09-15Add dependency to ruby-mini_portile. Noted by joerg@ and thanks!taca1-1/+5
2015-09-14Add support for ECDH, from upstreammanu4-3/+290
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
2015-09-14Changes 6.1.26:adam3-8/+11
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.
2015-09-13Reset PKGREVISION.taca1-2/+1
2015-09-13Update ruby-tiny_tds to 0.7.0.taca3-19/+22
* 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.
2015-09-13Upadte ruby-sequel to 4.26.0.taca3-7/+8
=== 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)
2015-09-13Update ruby-pg to 0.18.3.taca2-6/+6
== 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)
2015-09-12Update to libzdb-3.1 (2015-08-31)tnn2-6/+6
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
2015-09-09Add forgotten patch for atomic_init -> db_atomic_init change.joerg1-0/+22
2015-09-08Avoid overlap between db's atomic.h and stdatomic.h.joerg20-10/+366
2015-09-08Fix patch previously committed. Fixes PR pkg/50205.fhajny2-4/+4
2015-09-07Now that _STRIPFLAG_INSTALL is disabled by default on Darwin, remove manualjperkin1-6/+1
settings of INSTALL_UNSTRIPPED=yes for Darwin in individual packages.
2015-09-07Fix NetBSD<7 build issue by re-using a patch from lang/nodejs (v8).fhajny2-1/+50
2015-09-07Update to MySQL Cluster 7.4.7: this is mainly a bug fix release.jnemeth5-26/+138
pkgsrc change: delete one patch that has been upstreamed Changes in MySQL Cluster NDB 7.4.7 (5.6.25-ndb-7.4.7) (2015-07-13) MySQL Cluster NDB 7.4.7 is a new release of MySQL Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous MySQL Cluster releases. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.25 (see Changes in MySQL 5.6.25 (2015-05-29)). Functionality Added or Changed - Deprecated MySQL Cluster node configuration parameters are now indicated as such by ndb_config --configinfo --xml. For each parameter currently deprecated, the corresponding <param/> tag in the XML output now includes the attribute deprecated="true". (Bug #21127135) Bugs Fixed - Important Change; Cluster API: The Ndb::getHighestQueuedEpoch() method returned the greatest epoch in the event queue instead of the greatest epoch found after calling pollEvents2(). (Bug #20700220) - Important Change; Cluster API: Ndb::pollEvents() is now compatible with the TE_EMPTY, TE_INCONSISTENT, and TE_OUT_OF_MEMORY event types introduced in MySQL Cluster NDB 7.4.3. For detailed information about this change, see the description of this method in the MySQL Cluster API Developer Guide. (Bug #20646496) - Important Change; Cluster API: Added the method Ndb::isExpectingHigherQueuedEpochs() to the NDB API to detect when additional, newer event epochs were detected by pollEvents2(). The behavior of Ndb::pollEvents() has also been modified such that it now returns NDB_FAILURE_GCI (equal to ~(Uint64)0) when a cluster failure has been detected. (Bug #18753887) - After restoring the database metadata (but not any data) by running ndb_restore --restore_meta (or -m), SQL nodes would hang while trying to SELECT from a table in the database to which the metadata was restored. In such cases the attempt to query the table now fails as expected, since the table does not actually exist until ndb_restore is executed with --restore_data (-r). (Bug #21184102) References: See also Bug #16890703. - When a great many threads opened and closed blocks in the NDB API in rapid succession, the internal close_clnt() function synchronizing the closing of the blocks waited an insufficiently long time for a self-signal indicating potential additional signals needing to be processed. This led to excessive CPU usage by ndb_mgmd, and prevented other threads from opening or closing other blocks. This issue is fixed by changing the function polling call to wait on a specific condition to be woken up (that is, when a signal has in fact been executed). (Bug #21141495) - Previously, multiple send threads could be invoked for handling sends to the same node; these threads then competed for the same send lock. While the send lock blocked the additional send threads, work threads could be passed to other nodes. This issue is fixed by ensuring that new send threads are not activated while there is already an active send thread assigned to the same node. In addition, a node already having an active send thread assigned to it is no longer visible to other, already active, send threads; that is, such a node is longer added to the node list when a send thread is currently assigned to it. (Bug #20954804, Bug #76821) - Queueing of pending operations when the redo log was overloaded (DefaultOperationRedoProblemAction API node configuration parameter) could lead to timeouts when data nodes ran out of redo log space (P_TAIL_PROBLEM errors). Now when the redo log is full, the node aborts requests instead of queuing them. (Bug #20782580) References: See also Bug #20481140. - An NDB event buffer can be used with an Ndb object to subscribe to table-level row change event streams. Users subscribe to an existing event; this causes the data nodes to start sending event data signals (SUB_TABLE_DATA) and epoch completion signals (SUB_GCP_COMPLETE) to the Ndb object. SUB_GCP_COMPLETE_REP signals can arrive for execution in concurrent receiver thread before completion of the internal method call used to start a subscription. Execution of SUB_GCP_COMPLETE_REP signals depends on the total number of SUMA buckets (sub data streams), but this may not yet have been set, leading to the present issue, when the counter used for tracking the SUB_GCP_COMPLETE_REP signals (TOTAL_BUCKETS_INIT) was found to be set to erroneous values. Now TOTAL_BUCKETS_INIT is tested to be sure it has been set correctly before it is used. (Bug #20575424) References: See also Bug #20561446, Bug #21616263. - NDB statistics queries could be delayed by the error delay set for ndb_index_stat_option (default 60 seconds) when the index that was queried had been marked with internal error. The same underlying issue could also cause ANALYZE TABLE to hang when executed against an NDB table having multiple indexes where an internal error occured on one or more but not all indexes. Now in such cases, any existing statistics are returned immediately, without waiting for any additonal statistics to be discovered. (Bug #20553313, Bug #20707694, Bug #76325) - The multi-threaded scheduler sends to remote nodes either directly from each worker thread or from dedicated send threads, depending on the cluster's configuration. This send might transmit all, part, or none of the available data from the send buffers. While there remained pending send data, the worker or send threads continued trying to send in a loop. The actual size of the data sent in the most recent attempt to perform a send is now tracked, and used to detect lack of send progress by the send or worker threads. When no progress has been made, and there is no other work outstanding, the scheduler takes a 1 millisecond pause to free up the CPU for use by other threads. (Bug #18390321) References: See also Bug #20929176, Bug #20954804. - In some cases, attempting to restore a table that was previously backed up failed with a File Not Found error due to a missing table fragment file. This occurred as a result of the NDB kernel BACKUP block receiving a Busy error while trying to obtain the table description, due to other traffic from external clients, and not retrying the operation. The fix for this issue creates two separate queues for such requests: one for internal clients such as the BACKUP block or ndb_restore, and one for external clients such as API nodes and prioritizing the internal queue. Note that it has always been the case that external client applications using the NDB API (including MySQL applications running against an SQL node) are expected to handle Busy errors by retrying transactions at a later time; this expectation is not changed by the fix for this issue. (Bug #17878183) References: See also Bug #17916243. - On startup, API nodes (including mysqld processes running as SQL nodes) waited to connect with data nodes that had not yet joined the cluster. Now they wait only for data nodes that have actually already joined the cluster. In the case of a new data node joining an existing cluster, API nodes still try to connect with the new data node within HeartbeatIntervalDbApi milliseconds. (Bug #17312761) - In some cases, the DBDICT block failed to handle repeated GET_TABINFOREQ signals after the first one, leading to possible node failures and restarts. This could be observed after setting a sufficiently high value for MaxNoOfExecutionThreads and low value for LcpScanProgressTimeout. (Bug #77433, Bug #21297221) - Client lookup for delivery of API signals to the correct client by the internal TransporterFacade::deliver_signal() function had no mutex protection, which could cause issues such as timeouts encountered during testing, when other clients connected to the same TransporterFacade. (Bug #77225, Bug #21185585) - It was possible to end up with a lock on the send buffer mutex when send buffers became a limiting resource, due either to insufficient send buffer resource configuration, problems with slow or failing communications such that all send buffers became exhausted, or slow receivers failing to consume what was sent. In this situation worker threads failed to allocate send buffer memory for signals, and attempted to force a send in order to free up space, while at the same time the send thread was busy trying to send to the same node or nodes. All of these threads competed for taking the send buffer mutex, which resulted in the lock already described, reported by the watchdog as Stuck in Send. This fix is made in two parts, listed here: 1. The send thread no longer holds the global send thread mutex while getting the send buffer mutex; it now releases the global mutex prior to locking the send buffer mutex. This keeps worker threads from getting stuck in send in such cases. 2. Locking of the send buffer mutex done by the send threads now uses a try-lock. If the try-lock fails, the node to make the send to is reinserted at the end of the list of send nodes in order to be retried later. This removes the Stuck in Send condition for the send threads. (Bug #77081, Bug #21109605) - Cluster API: The pollEvents2() method now waits indefinitely for events when a negative value is used for the time argument. (Bug #20762291) - Cluster API: NdbEventOperation::isErrorEpoch() incorrectly returned false for the TE_INCONSISTENT table event type (see The Event::TableEvent Type). This caused a subsequent call to getEventType() to fail. (Bug #20729091) - Cluster API: Creation and destruction of Ndb_cluster_connection objects by multiple threads could make use of the same application lock, which in some cases led to failures in the global dictionary cache. To alleviate this problem, the creation and destruction of several internal NDB API objects have been serialized. (Bug #20636124) - Cluster API: A number of timeouts were not handled correctly in the NDB API. (Bug #20617891) - Cluster API: When an Ndb object created prior to a failure of the cluster was reused, the event queue of this object could still contain data node events originating from before the failure. These events could reference old epochs (from before the failure occurred), which in turn could violate the assumption made by the nextEvent() method that epoch numbers always increase. This issue is addressed by explicitly clearing the event queue in such cases. (Bug #18411034) References: See also Bug #20888668.
2015-09-06reset PKG_REVISION.taca3-6/+3
2015-09-03Import wip/php-rrd as converters/php-rrd.fhajny4-1/+24
The PECL/rrd extension provides bindings to the RRDtool C library.
2015-09-03sortjnemeth1-2/+2
2015-09-02Update hiredis to 0.13.2wiedi4-17/+19
* Prevent crash on pending replies in async code (Thanks, @switch-st) * Clear `REDIS_CONNECTED` flag when connection is closed (Thanks, Jerry Jacobs) * Add MacOS X addapter (Thanks, @dizzus) * Add Qt adapter (Thanks, Pietro Cerutti) * Add Ivykis adapter (Thanks, Gergely Nagy) All adapters are provided as is and are only tested where possible.
2015-09-02Import SQLRelay node.js API as databases/sqlrelay-nodejs.fhajny3-1/+28
2015-09-02Update databases/sqlrelay to 0.63.fhajny10-65/+116
sqlrelay 0.63 - suppressed ruby configure warning - fixed glib detection if pkg-config isn't present - fixed mono detection on freebsd - fixed node.js yes/no misreport bug in configure script - added freetds tcl test - fixed slashes in tcl tests for windows - updated docs to mention firebird buffer size parameters - updated MAX_ITEM_BUFFER_SIZE to 32768 for firebird - fixed ruby detection on fedora 22 - fixed missing export for setAuth/ResponseTimeout in ruby api - added manual include of inttypes.h in php api to work around issue with define/undef games, revealed on openbsd 5.7 - tweaked ruby cflags script for debian 8 - refactored mysql detection - tweaked unixodbc detection to also look in /usr/include/odbc - renamed "oracle8" connection plugin to "oracle" - renamed "sybase" connection plugin to "sap" - updated identity tests in api's/cmdline clients to use charstring::contains() rather than !charstring::compare() - implemented missing destructors for ADO.NET Data Provider sqlrelay 0.62 - added query filter plugin framework - added regex, string and pattern filters - added normalization translation - added reformatdatetime result set translation - fixed error in sqlrconfigfile class that could cause sqlr-start to crash if one instance defines addresses but the next doesn't - added query status flag to sqlrservercursor - tweaked odbc driver's SQLGetTypeInfo() - field name is passed into runResultSetTranslations() now - added support for maxitembuffersize, maxselectlistsize, and maxbindcount for firebird - added native api for node.js - added recognition of bigint, ubigint and uniqueidentifier fields in freetds/sybase - added nullsasnulls command to sqlrsh - added workaround for freetds empty (but non-null) text fields not getting properly converted to null-terminated empty strings - fetchatonce, maxitembuffersize and maxselectlistsize are set to defaulting values if invalid values are given for them - added lazyconnect option to PHP PDO and Perl DBI drivers (defaults to 1) - direct Transact SQL which returns a result set is now supported with Sybase/SAP/MSSQLServer/FreeTDS - added docs for authentication, query translation, query filter and result set translation modules - added -fPIC to sqlrserver-config --cflags, if supported - the "default" auth module is now called "userlist" - added database auth module that is analagous to authtier="database" - replaced passwordencryption attribute with passwordencryptionid - added --disable-postgresql8-api configure option - tweaked -Werror detection in configure script - refactored sqlr-bench build to work on windows - documentation, examples and tests are now covered by a license - reflecting modern interpretation of the GPL, The license for The SQLRelay Server (as designated in COPYING) license now carries an exception, explicitly allowing it to be linked with various non-GPL compatible libraries - license is installed now sqlrelay 0.61 skipped sqlrelay 0.60 - fixed true->false transposition in sqlrservercontroller::interceptQuery that could lead to a reLogIn loop - disabled -Werror for gcc < 2.7 - applied George Carrette's patch to fix PDO connectstring options - migrated directory/file paths info into sqlrpaths class - removed undocumented and not-so-relevent-these-days MAX_CONNECTIONS/overridemaxconnections failsafe in sqlr-start - fixed java header detection for javac located in /usr/bin - updated java api to support non-null-tolerant implementations of environment::NewStringUTF() - the perl api builds correctly on OSR5 again - the postgresql sslmode is omitted entirely from the connect string now, if it's disabled, to prevent problems with older versions of postgresql that don't support the parameter at all - mono 2.8 or greater is required now - added a datedelimiters attribute to the instance tag in sqlrelay.conf to limit what date delimiters are used when translating dates - re-added mssqlserver detection, which had been accidentally removed - fixed statically-linked build - fixed mysql lob field bug that could cause a crash