fix db2 = null issue
test db2 is null fix
roll out x-mass release 1.3.4 love and peace to y'all!
Merge pull request #506 from pierrickrouxel/db2_is_null_fix

[DB2] fix db2 = null issue
[Firebird] Insert quotes for blobs to prevent failed inserts on not-null cols, Remove table names from SET clause in SQL update
Merge pull request #519 from rzane/master

[Firebird] Not-null blobs and remove table names from set clause in update statement
Initialize update_lob_values
[rails 4.1] create_table_definition changed from 3 to 4 parameters
appraisal rails 4.1 to beta1
update appraisals - most importantly rails 4.1 (master)
[mysql] fix incompatible character encodings: ASCII-8BIT and UTF-8
... triggered with Rails 4.1 (master)
rails 4.1 shall no longer fail!
update MySQL Connector/J to 5.1.28
Downgrade RubyGems to 2.1.11 in 1.8 mode

This issue is fixed by 2.2.1, but until Travis VM is upgraded to use it,
we need this hack.
boost an ego - standing on the shoulders of AR-JDBC giants + spec license
spec the license(s) before the license police catches us bare gem-ed
return "early" from jndi: configurations (no driver loading, url completion etc)
DRY-out config detection for a jndi connection + add some connection tests
"new" recommended jndi: adapter configuration for less confusion + (c) 2014
travis-ci : try `gem update --system` for all