This repository has been archived by the owner. It is now read-only.
Switch branches/tags
Nothing to show
Commits on Mar 5, 2015
  1. Merge pull request #24 from blocktrail/escapefield

    DrBenton committed Mar 5, 2015
    use the escapeField function when doing .insert or .update
Commits on Jan 22, 2015
  1. Merge pull request #33 from vlucas/master

    DrBenton committed Jan 22, 2015
    Add support for Postgres DSN, i.e. DATABASE_URL
Commits on Jan 21, 2015
Commits on Apr 7, 2014
Commits on Jan 14, 2014
  1. better "falsy" values management

    DrBenton committed Jan 14, 2014
    * falsy-but-not-Numbers-and-not-null values are converted to blank Strings
    * added a "SQL injection prevention" unit test
    * version bumped to 0.7.1
Commits on Jan 13, 2014
  1. bump version to 0.7

    DrBenton committed Jan 13, 2014
  2. Fixed #16

    DrBenton committed Jan 13, 2014
    * DBWrapper#close() is now documented in the README
  3. dropped Node 0.6 support

    DrBenton committed Jan 13, 2014
    * seems that some of our dependencies are not compatible with Node 0.6 anymore (@see )
  4. Fixed #19

    DrBenton committed Jan 13, 2014
    * DBSelect : we now handle "falsy" params correctly
    * DBSelect : a "null" param is now converted to NULL in the SQL String
    * auto formatting on dbSelect.js
  5. Fixed #20

    DrBenton committed Jan 13, 2014
    * more accurate String params escaping
  6. Node-DBI 2014 modernization :-)

    DrBenton committed Jan 13, 2014
    * removed Vows, replaced by the Mocha&Chai duo for unit tests
    * removed Underscore, replaced by Lodash
    * added a Makefile - tribute to TJ Holowaychuck ;-)
    * added Vagrantfile & Vagrant VM init script for Ubuntu
Commits on Aug 27, 2013
  1. 0.6.2

    kalifg committed Aug 27, 2013
  2. Updated mysql dependency

    kalifg committed Aug 27, 2013
    For some reason specifying "0.9.x" for mysql version pulled only their
    latest branch (0.9.0) and not the latest tag (0.9.6).
    I was receiving this error from 0.9.0:
    > /home/mdwyer/Desktop/src/TAMU-btsync/iris/tamu-ldap-proxy/node_modules/node-dbi/node_modules/mysql/lib/mysql/net_constan
    > ts.js:8
    > module.exports = process.binding('net');
    >                          ^
    > Error: No such module
    >     at Object.<anonymous> (/home/mdwyer/Desktop/src/TAMU-btsync/iris/tamu-ldap-proxy/node_modules/node-dbi/node_modules/
    > mysql/lib/mysql/net_constants.js:8:26)
    >     at Module._compile (module.js:449:26)
    >     at Object.Module._extensions..js (module.js:467:10)
    >     at Module.load (module.js:356:32)
    >     at Function.Module._load (module.js:312:12)
    >     at Module.require (module.js:362:17)
    >     at require (module.js:378:17)
    >     at Object.<anonymous> (/home/mdwyer/Desktop/src/TAMU-btsync/iris/tamu-ldap-proxy/node_modules/node-dbi/node_modules/
    > mysql/lib/mysql/client.js:10:20)
    >     at Module._compile (module.js:449:26)
    >     at Object.Module._extensions..js (module.js:467:10)
    This is fixed in
Commits on Sep 16, 2012
  1. Travis CI tests passed successfully

    DrBenton committed Sep 16, 2012
     * misc Unit tests fixes & optimizations
     * add Travis CI build status in
  2. PostgreSQL driver now returns JS dates

    DrBenton committed Sep 16, 2012
    * README update
    * Unit tests fixes
  3. README & .travis.yml update

    DrBenton committed Sep 16, 2012
    * DB setup must follow Travis CI requirements
    * added Node.js 0.6 to .travis.yml
  4. Add hook

    DrBenton committed Sep 16, 2012
Commits on Sep 6, 2012
  1. Merge pull request #9 from mlaccetti/master

    DrBenton committed Sep 6, 2012
    Updated the README to include connect() info
  2. Tweak to the README

    mlaccetti committed Sep 6, 2012
    Not sure if this is necessary, but it seems that calling
    DbWrapper.connect() is the magic that really makes things happen.
    Tweaked the README to show where that might take place and included the
    info in the list of API functions.
Commits on Aug 17, 2012
  1. Merge pull request #5 from kalifg/where-parenthesis

    DrBenton committed Aug 17, 2012
    Version bump for new SQL queries parentheses better management features.
Commits on Aug 14, 2012
  1. Version bump for new features.

    kalifg committed Aug 14, 2012
  2. Merge pull request #4 from kalifg/where-parenthesis

    DrBenton committed Aug 14, 2012
    Where parenthesis
  3. Added new test dealing with compound where clauses and array values.

    kalifg committed Aug 14, 2012
    Updated README with information about supplying array values to
    Fixed bug in .where() so that array values are treated as they are in
    ZendDb, with the possible exception that we are not restricting what
    clauses they can be supplied to.
    Tests pass.
  4. This update will cause all where clauses to be parenthesized, allowing

    kalifg committed Aug 14, 2012
    one to group compound statements such as .where('id=? OR name=?) which
    the same grouping expectations as they would have with ZendDb.
    Updated tests and README for proposed changes.
  5. Merge pull request #3 from kalifg/orWhere

    DrBenton committed Aug 14, 2012
Commits on Aug 9, 2012
Commits on Aug 8, 2012
  1. Added documentation about new where features.

    kalifg committed Aug 8, 2012
    Added name to package.json under authors section.
Commits on Aug 3, 2012
  1. Added new functions DBSelect.whereGroup(groups) and

    kalifg committed Aug 3, 2012
    These function will allow the creation of arbitrary parenthetical
    expressions in the WHERE clause.  Each has a parameter specifying how
    many groups to open or close.  It's smart enough to not close groups
    that aren't open and to automatically close open groups even if you
    forget to.
    As an example, this:
              .whereGroupClose() // Erroneous whereGroupClose to be handled
              .whereGroup(3)     // Multiple group start
              .where( 'id=?', 10 )
              .where( 'first_name=?', 'Dr.')
              .where( 'last_name LIKE ?', '%Benton%' )
              .orWhere( 'nickname=?', 'dude' )
              // Automatic closing of leftover groups
    Generates this:
    "SELECT user.* FROM user WHERE (((enabled=1 AND id=10) AND
    first_name='Dr.' AND (last_name LIKE '%Benton%' OR nickname='dude')))"
Commits on Aug 2, 2012
  1. The function DBSelect.where now has an optional third parameter that

    kalifg committed Aug 2, 2012
    specifies whether to use OR instead of AND for the current clause.
    Added the function DBSelect.orWhere to give it parity with ZendDB.
    Modified the function DBSelect.assemble to take advantage of this