Permalink
Commits on Oct 13, 2017
  1. Merge pull request #910 from FredDeschenes/bean-functions-binding

    qualidafial committed Oct 13, 2017
    WIP: Bean functions binding
Commits on Oct 12, 2017
  1. Merge pull request #912 from jdbi/rm-txn-isolation-anno

    qualidafial committed Oct 12, 2017
    Remove @TransactionIsolation in favor of @Transaction
  2. Remove `@TransactionIsolation` in favor of `@Transaction`

    qualidafial committed Oct 12, 2017
Commits on Oct 10, 2017
Commits on Oct 9, 2017
  1. Merge pull request #909 from jdbi/row-mapper-findfor-refactor

    qualidafial committed Oct 9, 2017
    Extract row-or-column mapper failback into its own config class
  2. Merge pull request #906 from jdbi/binding_check

    arteam committed Oct 9, 2017
    Add a check for mistyped named parameters
  3. Add release notes for findRowMapperFor(...) refactor.

    qualidafial committed Oct 9, 2017
  4. Extract row-or-column mapper failback into its own config class, so c…

    qualidafial committed Oct 9, 2017
    …ode can tell whether a row mapper is registered for a given type.
Commits on Oct 8, 2017
  1. Merge pull request #907 from jdbi/type-missing-error

    qualidafial committed Oct 8, 2017
    Improve error message thrown when a generic type cannot be inferred and you must #bindByType
  2. Improve error message thrown when a generic type cannot be inferred a…

    stevenschlansker committed Oct 8, 2017
    …nd you must #bindByType
Commits on Oct 6, 2017
Commits on Oct 5, 2017
  1. Add a check for mistyped named parameters

    arteam committed Oct 2, 2017
    It's very easy to mistype an SQL query and use a column name instead of
    a naming parameters. For example, `DELETE FROM users WHERE id=id` instead
    of `DELETE FROM users WHERE id=:id`. Unfortunatelly, this query is a valid
    SQL query and a DBMS will happily execute it. Such mistake is very easy to
    make, relatively hard to catch with a unit test and can lead to a disaster
    in production.
    
    It would be great if JDBI could detect situations when the user added
    a binding, but the query doesn't have any named parameters.
  2. PreparedBatch: update context binding for each batch

    stevenschlansker committed Sep 28, 2017
    Otherwise, anyone who uses the context to print out debug information
    (say an exception) just has an empty binding which is misleading.
  3. Basic ResultProducer and TimingCollector docs

    stevenschlansker committed Sep 27, 2017
    Fixes #732
Commits on Oct 4, 2017
  1. Merge pull request #893 from jdbi/empty-batch-add

    qualidafial committed Oct 4, 2017
    PreparedBatch: throw an exception if you add() a batch with no bindings at all
  2. Merge pull request #903 from FredDeschenes/bindbean-use-public-fields

    qualidafial committed Oct 4, 2017
    Use public fields as well as getters for 'bindBean'
Commits on Oct 3, 2017
  1. Merge pull request #900 from jdbi/docs-sql-object

    qualidafial committed Oct 3, 2017
    More docs for SQL Object
Commits on Oct 2, 2017
  1. Reorganize tutorial: split out basic and advanced sections. Add secti…

    qualidafial committed Oct 2, 2017
    …on for decorating annotations.
Commits on Sep 27, 2017
  1. PreparedBatch: throw an exception if you add() a batch with no bindin…

    stevenschlansker committed Sep 27, 2017
    …gs at all
  2. Rename ResultSetMapper to ResultSetScanner

    stevenschlansker committed Sep 27, 2017
    The name 'mapper' is already used for a different concept
  3. Whitespace fix.

    stevenschlansker committed Sep 27, 2017
  4. Simple Configuration documentation

    stevenschlansker committed Sep 5, 2017
    Fixes #719
Commits on Sep 14, 2017
Commits on Sep 12, 2017
  1. Basic StatementContext doc.

    stevenschlansker committed Sep 5, 2017
    Fixes #731
Commits on Sep 5, 2017
  1. Merge pull request #880 from jdbi/forward-only

    stevenschlansker committed Sep 5, 2017
    Make Statement processing FORWARD_ONLY by default for performance.
Commits on Aug 29, 2017