in postgres 9, this change allows the specs to pass on any version.
cCommand_execute_non_query() assumes that when a returned status from PostgreSQL is PGRES_TUPLES_OK that there is always at least one tuple in the set. This is not always the case as we have at least one INSERT query with the RETURNING option which always returns a null set due to a valid database trigger.
Signed-off-by: Alex Coles <email@example.com>
* Use 0.7.0 not 0.7.1. Commit 9612e9f in rake-compiler allows for compilation of experimental JRuby C-extensions -- but breaks our setup which relies on this being a no-op when running on JRuby. Signed-off-by: Alex Coles <firstname.lastname@example.org>
* Use the Gemfile gemspec method to avoid declaring dependencies twice. * [data_objects] Declare a quality group based on DM quality dependencies. These tools are not yet in use though and only make sense for projects that are pure Ruby (namely data_objects). Signed-off-by: Alex Coles <email@example.com>
… it is only a string this might improve compability with legacy data