Commits on Jun 13, 2017
  1. Override Dataset#as_hash instead of #to_hash if #as_hash is defined

    Sequel 4.48.0 will rename Dataset#to_hash to #as_hash, with a
    to_hash alias that calls as_hash.  This will allow both
    Dataset#to_hash and #as_hash to use the optimized version
    on Sequel 4.48.0+.  For backwards compatibility, if as_hash
    isn't defined, alias as_hash to to_hash and then remove as_hash.
    committed Jun 13, 2017
  2. Use PG::Error instead of PGError if available, avoiding deprecation w…

    …arning on pg 0.21.0+, bump version to 1.6.19
    committed Jun 13, 2017
Commits on Apr 27, 2017
  1. Bump version to 1.6.18

    committed Apr 27, 2017
  2. Remove Rakefile.cross

    sequel_pg hasn't been supported on Windows in a long time, there
    doesn't seem to be a reason to keep this.
    committed Apr 27, 2017
  3. Bump copyright year

    committed Apr 27, 2017
Commits on Apr 26, 2017
  1. Support logging of connection information in single row mode

    log_yield has been deprecated in Sequel, and will be removed from
    Sequel 5.  Switch to log_connection_yield, which allows the
    logging of connection info with queries.
    Still support previous versions of Sequel by using log_yield
    if log_connection_yield is not available.
    committed Apr 26, 2017
Commits on Feb 6, 2017
  1. Store version in C file

    committed Feb 6, 2017
Commits on Nov 16, 2016
  1. Remove verbose mode warnings

    committed Nov 16, 2016
Commits on May 26, 2016
  1. Minor spelling corrections

    docelic committed May 26, 2016
Commits on Apr 29, 2016
  1. Bump version to 1.6.17

    committed Apr 29, 2016
Commits on Apr 25, 2016
Commits on Apr 11, 2016
  1. Work with upcoming Sequel 4.34.0 release, bump version to 1.6.15

    This requires a dependency on Sequel 4.0 due to the use of
    Sequel::OPTS.  It's been almost 3 years since Sequel 4's release,
    so this shouldn't be a problem.
    committed Apr 11, 2016
Commits on Jan 19, 2016
Commits on Jun 29, 2015
Commits on Mar 23, 2015
  1. Fix segfault when Dataset#yield_hash_rows is passed a nil value when …

    …using ruby pg 0.18+, bump version to 1.6.12 (Fixes #19)
    This can happen when swallowing errors inside Database#log_yield.
    This issue only affected sequel_pg 1.6.11, as the bug was in the
    pg 0.18+ support code and older versions of sequel_pg do not
    support pg 0.18+.
    committed Mar 23, 2015
Commits on Feb 26, 2015
Commits on Nov 6, 2014
  1. Update README

    committed Nov 6, 2014
Commits on Nov 4, 2014
  1. Work with ruby pg 0.18+ (currently a prerelease), bump version to 1.6.11

    ruby-pg 0.18 changes the internals so that the data objects that
    were previously pointers to PGconn and PGresult are now structs
    that contain pointers to PGconn or PGresult.
    If ruby-pg 0.18+ is detected (currently using
    defined?(PG::TypeMapAllStrings)), then this changes the code to
    use ruby-pg C functions that return the underlying pointers.
    The only other change is the error message when too many columns
    are used now includes the actual number of columns, instead of
    just the maxinum number allowed.
    committed Nov 4, 2014
Commits on Jul 11, 2014
  1. Work correctly when the database timezone is not a named timezone but…

    … the application timezone is
    Also, bump version to 1.6.10
    committed Jul 11, 2014
Commits on May 11, 2014
Commits on Mar 5, 2014
  1. When using the streaming extension, automatically use streaming to im…

    …plement paging in Dataset#paged_each
    Bump version to 1.6.9.
    committed Mar 5, 2014
Commits on Aug 9, 2013
Commits on Aug 5, 2013
  1. Add license to gemspec

    committed Aug 5, 2013
  2. Allow overriding maximum allowed columns in a result set via -- --wit…

    …h-cflags=\"-DSPG_MAX_FIELDS=1600\" (Fixes #12)
    Previously, you couldn't override this limit without modifying
    the source code.
    committed Aug 5, 2013
  3. Remove unused struct

    This was left over from the PQsetRowProcessor streaming support.
    committed Aug 5, 2013
Commits on Jun 6, 2013
Commits on May 31, 2013
  1. Work correctly when using the named_timezones extension, bump version…

    … to 1.6.6
    This turns out to be a fairly easy change, since we just call
    Database#to_application_timestamp with the string if we don't
    recognize the timezone.
    committed May 31, 2013
Commits on Mar 15, 2013
  1. Work around format-security false positive (Fixes #9)

    Even though the rb_raise call is provably safe (static function
    called with all static arguments), format-security still complains.
    To appease it and make sequel_pg work in setups where
    -Werror=format-security is used by default, use "%s" as the format
    committed Mar 15, 2013
Commits on Mar 6, 2013