Skip to content
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 …

    committed
    …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+.
Commits on Feb 26, 2015
Commits on Nov 6, 2014
  1. Update README

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

    committed
    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.
Commits on Jul 11, 2014
  1. Work correctly when the database timezone is not a named timezone but…

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

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

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

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

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

    committed
    … 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.
Commits on Mar 15, 2013
  1. Work around format-security false positive (Fixes #9)

    committed
    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
    string.
Commits on Mar 6, 2013
Commits on Jan 14, 2013
  1. Remove type conversion of int2vector and money types on PostgreSQL, s…

    committed
    …ince previous conversions were wrong (Fixes #8)
    
    A similar change was made in Sequel about 6 months ago.
    
    Bump version to 1.6.4.
Commits on Nov 30, 2012
  1. Make streaming support not swallow errors when rows are not retrieved…

    committed
    …, bump version to 1.6.3
    
    If the user doesn't retrieve all of the rows when streaming, sequel_pg
    is supposed to flush the connection by manually retrieving the other
    rows.  Before, it wasn't checking the result status of each result,
    causing it to miss errors.
    
    I noticed this after adding an integration test for deferred foreign
    key support to Sequel.
Commits on Nov 16, 2012
  1. Bump version to 1.6.2

    committed
Commits on Nov 11, 2012
  1. @dbussink

    Don't register variables on the stack as global

    dbussink committed
    By definition, VALUE pointers on the stack can never be a global variable.
    The location goes out of scope when the function is executed and
    can point at random data.
    
    On the other hand, the error class is used as global so mark it as such.
Commits on Oct 25, 2012
  1. Make PostgreSQL array parser handle string encodings correctly on rub…

    committed
    …y 1.9, bump version to 1.6.1
    
    This copies the encoding of the embedded array string to each member
    of the array.  It simplifies the logic somewhat, and also marks each
    string as tainted, similar to the default logic to retrieve values.
Commits on Sep 10, 2012
Commits on Sep 4, 2012
  1. Bump version to 1.6.0

    committed
    Bump the dependency on sequel to 3.39.0.  The streaming support
    requires pg 0.14.1, but as most people won't be using it, I am
    leaving the dependency on pg at 0.8.0.
Commits on Aug 9, 2012
  1. Replace PQsetRowProcessor streaming with PQsetSingleRowMode streaming…

    committed
    … introduced in PostgreSQL 9.2beta3
    
    PostgreSQL decided that PQsetRowProcessor was a bad API, and replaced
    it with PQsetSingleRowMode in 9.2beta3.  I agree with the choice, as
    the new API is simpler and fairly easy to use.
    
    Currently, this requires a patch to ruby-pg to recognize
    PGRES_SINGLE_TUPLE as an OK result status.  That should hopefully
    be committed soon.  This also requires the master branch of Sequel,
    as it depends on some recent refactoring in the Sequel postgres
    adapter.
Commits on Aug 2, 2012
Commits on Jul 25, 2012
Commits on Jun 29, 2012
  1. Bump version to 1.5.0

    committed
Commits on Jun 25, 2012
  1. Add PostgreSQL array parser

    committed
    This adds a C-based PostgreSQL array parser.  The original
    implementation is from the pg_array_parser library, but I've
    heavily modified it.  This C-based parser is 5-500 times faster
    than the pure ruby parser that Sequel uses by default.  5 times
    faster for an empty array, and 500 times faster for an array
    with a single 10MB string.
    
    Because the pg_array extension can be loaded before or after
    sequel_pg, handle the case where it is loaded after by switching
    the Creator class to use the C based parser instead of the pure
    ruby parser.
Commits on Jun 1, 2012
  1. Bump version to 1.4.0

    committed
Commits on May 21, 2012
Something went wrong with that request. Please try again.