Commits on May 4, 2012
  1. Documentation tweaks

    committed May 4, 2012

    committed May 4, 2012
  3. Remove the RawResult type

    committed May 4, 2012
  4. Borrow :. from ozataman

    See commit cd76bea
    committed May 4, 2012
Commits on Mar 18, 2012
Commits on Mar 11, 2012
Commits on Mar 8, 2012
  1. Fix up some warnings

    committed Mar 8, 2012
  2. Merge branch 'master' of into 0.1

    committed Mar 8, 2012
  3. Merge pull request #13 from joeyadams/master

    Use exception mask in withTransactionMode, and compile with -Wall
    committed Mar 8, 2012
Commits on Mar 4, 2012
  1. Change the FromRow instances to applicative style

    The concerns detailed in 5f045cc should
    now be taken care of by the revised interface.
    Namely, the Ok constructor must be forced in order to determine whether
    or not an exception is thrown,  and the Ok constructor evaluates it's
    argument to whnf.
    committed Mar 4, 2012
  2. Add DefaultIsolationLevel as a distinct option

    It turns out that by default,  "BEGIN" usually means the same as
    "BEGIN ISOLATION LEVEL READ COMMITTED", but this isn't necessarily so.
    committed Mar 4, 2012
Commits on Mar 3, 2012
Commits on Mar 2, 2012
Commits on Feb 23, 2012
  1. Modify Result into FromField

    committed Feb 23, 2012
Commits on Feb 9, 2012
  1. Bump version to 0.0.5

    committed Feb 9, 2012
  2. Convert some mysql-simple documentation to postgresql-simple

    This note is a holdover from mysql-simple, and it has been
    obsolete from the very first release of postgresql-simple.
      * Ensure that any ResultError that might arise is thrown immediately, rather than some place later in application code that cannot handle it.
    This issue has been taken care of by the switch to the Either type,
    Thanks to Doug Beardsley for bringing this to my attention.
    committed Feb 9, 2012
Commits on Feb 8, 2012
  1. Don't store floating point NaNs and Infinites as NULL

    Unlike MySQL, PostgreSQL can store these values without trouble.  However,
    what PostgreSQL does with these values in database-side computations isn't
    the most sensible.   I still think it's better to represent these values
    committed Feb 8, 2012
Commits on Feb 6, 2012
  1. Export returnError

    committed Feb 6, 2012
Commits on Jan 30, 2012
  1. Export defaults

    committed Jan 30, 2012
Commits on Jan 27, 2012
  1. Add support for isolation levels

    Thanks to Philip Weaver for the suggestion
    committed Jan 27, 2012
Commits on Jan 25, 2012
  1. Second attempt at implementing `fold`

    This solves all the issues mentioned in bce0d38
    This should be the first implementation in the right ballpark with regard
    to correctness.  However, there is still room for improvement:
    1. Error messages
         A. appears to come from "query", "execute", etc.
         B. queries appear with parameters substituted
    2. Network performance
         A. eliminate a round trip on start up when the fold is auto-wrapped in
              a transaction
         B. eliminate a round trip on start up by fetching the first rows at the
              same time the cursor is opened
         C. often eliminate a round trip at the end by detecting when there
              are fewer rows than requested.
         D. interleave processing and network IO to a better degree
    3. Haskell performance
         A.  No need to marshal a block of rows into a list before feeding them
              to the folding function.
    committed Jan 25, 2012