upsert 2.9.10-java

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 7eb840a86c1973e535fae818ad6212aeae072512
+  data.tar.gz: 617afaddc0e769d688a4e3dba95e9beeef436596
+SHA512:
+  metadata.gz: 900bce378101ac8da7235eb365f9a1b568b5d95480c9a32193186aaa34293b7ea1efb2af6557c833604646b9bd1b052bc3bc80bc384497e627b24039666078f9
+  data.tar.gz: 5d48a452e7d60bab795739152ddae77f169fca3685d21b3b931bf0f73998ac1af37ce9332d68a885873e2d07cf198125369b721dcae54ac48c11dd4d6edfe9e2

data/.gitignore

@@ -0,0 +1,19 @@
+.DS_Store
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+*.log

data/.ruby-version

@@ -0,0 +1 @@
+jruby-9.1.17.0

data/.standard.yml

@@ -0,0 +1 @@
+ruby_version: 2.2.4

data/.travis.yml

@@ -0,0 +1,63 @@
+dist: xenial
+language: ruby
+cache: bundler
+services:
+  - docker
+rvm:
+  - 2.6
+  - 2.5
+  - 2.4
+  - 2.3
+  - 2.2
+  - jruby-9.1.14.0
+  - jruby-9.1.17.0
+  - jruby-9.2.7.0
+env:
+  global:
+  - USERNAME=travis
+  - PASSWORD=
+  - DB_USER=upsert_test
+  - DB_PASSWORD=upsert_test
+  - DB_NAME=upsert_test
+  matrix:
+    - DB=postgresql DB_VERSION=postgres:9.4
+    - DB=postgresql DB_VERSION=postgres:9.5
+    - DB=postgresql DB_VERSION=postgres:9.6
+    - DB=postgresql DB_VERSION=postgres:10
+    - DB=postgresql DB_VERSION=postgres:11
+    - DB=postgresql DB_VERSION=postgres:12
+    - DB=postgresql DB_VERSION=postgres:9.4 UNIQUE_CONSTRAINT=true
+    - DB=postgresql DB_VERSION=postgres:9.5 UNIQUE_CONSTRAINT=true
+    - DB=postgresql DB_VERSION=postgres:9.6 UNIQUE_CONSTRAINT=true
+    - DB=postgresql DB_VERSION=postgres:10 UNIQUE_CONSTRAINT=true
+    - DB=postgresql DB_VERSION=postgres:11 UNIQUE_CONSTRAINT=true
+    - DB=postgresql DB_VERSION=postgres:12 UNIQUE_CONSTRAINT=true
+    - DB=mysql DB_VERSION=mysql:5.6
+    - DB=mysql DB_VERSION=mysql:5.7
+    - DB=mysql DB_VERSION=mysql:8
+matrix:
+  exclude:
+    - rvm: 2.6
+      env: DB=postgresql DB_VERSION=postgres:9.4
+    - rvm: 2.6
+      env: DB=postgresql DB_VERSION=postgres:9.5
+    - rvm: 2.6
+      env: DB=postgresql DB_VERSION=postgres:9.4 UNIQUE_CONSTRAINT=true
+    - rvm: 2.6
+      env: DB=postgresql DB_VERSION=postgres:9.5 UNIQUE_CONSTRAINT=true
+    - rvm: jruby-9.2.7
+      env: DB=postgresql DB_VERSION=postgres:9.4
+    - rvm: jruby-9.2.7
+      env: DB=postgresql DB_VERSION=postgres:9.5
+    - rvm: jruby-9.2.7
+      env: DB=postgresql DB_VERSION=postgres:9.4 UNIQUE_CONSTRAINT=true
+    - rvm: jruby-9.2.7
+      env: DB=postgresql DB_VERSION=postgres:9.5 UNIQUE_CONSTRAINT=true
+  allow_failures:
+    - env: DB=postgresql DB_VERSION=postgres:12
+    - env: DB=postgresql DB_VERSION=postgres:12 UNIQUE_CONSTRAINT=true
+before_install:
+  - ./travis/run_docker_db.sh
+  - bundle --version
+  - gem --version
+script: ./travis/run_specs.sh

data/.yardopts

@@ -0,0 +1,2 @@
+--no-private
+--readme README.md

data/CHANGELOG

@@ -0,0 +1,265 @@
+-- no version -- / 2019-06-05
+
+* Enhancements
+
+  * Bump development Ruby version to 2.5 since Ruby 2.2 is no longer supported.
+  This should not affect usage of the gem, only local development for people
+  working *on* the gem. Ruby 2.2 is also not dropped from Upsert compatibility
+  at this time but you should consider upgrading to newer Ruby versions anyway.
+
+2.2.1 / 2017-04-20
+
+* Bug fixes
+
+  * Fix unique constraint detection on pg >9.5.5 (@pnomolos https://github.com/seamusabshere/upsert/pull/99)
+  * Fix Ruby 1.9 tests
+
+2.2.0 / 2017-04-14
+
+* Enhancements
+
+  * Use native "upsert" on Postgres 9.5+! (thanks to @pnomolos https://github.com/seamusabshere/upsert/pull/79)
+  * More modern CI tests
+
+2.1.2 / 2016-02-25
+
+* Enhancements
+
+  * Test on Ruby 2.3 - thanks @Ch4s3 https://github.com/seamusabshere/upsert/pull/70
+
+* Bug fixes
+
+  * Stop using Thread.exclusive - thanks @hpetru https://github.com/seamusabshere/upsert/pull/67
+
+2.1.1 / 2016-02-12
+
+* Enhancements
+
+  * Assume function exists to avoid huge amounts of recreation
+
+2.1.0 / 2015-03-13
+
+* Bug fixes
+
+  * Thread safety with Sidekiq! thanks @evadne and @thbar ! https://github.com/seamusabshere/upsert/pull/47
+
+* Known issues
+
+  * speed_spec fails against activerecord-import on mysql... need some advice on properly testing it
+
+2.0.4 / 2015-01-27
+
+* Bug fixes
+
+  * Support mysql returning column info as symbols - thanks @pnomolos
+
+* Enhancements
+
+  * Travis and misc test fixes - thanks @raviolicode
+  * Backwards compat with 1.8 - thanks @raviolicode
+
+2.0.3 / 2013-11-27
+
+* Bug fixes
+
+  * Add parentheses to equality expressions
+
+* Enhancements
+
+  * On Postgres, use (A = B OR (A IS NULL AND B IS NULL)) instead of A IS NOT DISTINCT FROM B because the latter does not use indexes
+  * pass :eager_nullify => false as the third argument to Upsert#row to disable clearing of null HStore keys
+
+2.0.2 / 2013-11-06
+
+* Bug fixes
+
+  * Properly check for NULL equality when creating the UPSERT functions - thanks @pnomolos - https://github.com/seamusabshere/upsert/issues/25
+  * When using Mysql2 client (MRI), don't pass timezone to DateTime columns - thanks @kjeremy! - https://github.com/seamusabshere/upsert/issues/24
+
+2.0.1 / 2013-07-24
+
+* Bug fixes
+
+  * Rookie mistake - gsub!'ed an input arg, sorry. Blew up on a frozen string, thank goodness.
+
+2.0.0 / 2013-07-24
+
+* Breaking changes
+
+  * For Postgres Hstore, null keys are deliberately deleted - so there's no way to set "foo" => NULL - "foo" will just get deleted as a key
+  * Name merge functions "upsert1_2_0" instead of "upsert_"
+
+1.2.0 / 2013-04-04
+
+* Breaking changes
+
+  * columns named "created_at" and "created_on" will only be set if it's a new row - thanks @derekharmel! https://github.com/seamusabshere/upsert/pull/15
+
+* Enhancements
+
+  * Detect invalid columns passed in either selector or setter - inspired by @atandrau, thanks! https://github.com/seamusabshere/upsert/issues/18
+
+* Bug fixes
+
+  * Always convert symbols to strings when used as bind vars - thanks @towerhe! - https://github.com/seamusabshere/upsert/pull/16
+
+1.1.7 / 2013-01-15
+
+* Enhancements
+
+  * :assume_function_exists option to avoid creating same merge function over and over
+  * Don't die on first occurrence of "tuple concurrently updated"
+
+1.1.6 / 2012-12-20
+
+* Bug fixes
+
+  * Require pg-hstore >=1.1.1 which doesn't escape single quotes and backslashes when output is going to be used in a bind variable (as it is here)
+
+1.1.5 / 2012-12-10
+
+* Bug fixes
+
+  * Properly cast "timestamp without time zone" in postgres - thanks @markmarijnissen! https://github.com/seamusabshere/upsert/issues/11
+
+1.1.4 / 2012-12-06
+
+* Enhancements
+
+  * Use latest pg-hstore gem with standardized namespace
+
+1.1.3 / 2012-12-06
+
+* Bug fix
+
+  * Don't die/fail trying to update an HStore column that has reverted to NULL.
+
+1.1.2 / 2012-12-06
+
+* Enhancements
+
+  * Support for PostgreSQL's HStore
+
+1.1.1 / 2012-12-03
+
+* Bug fixes
+
+  * Removed inadvertent dependency on ActiveSupport - thanks @thbar! https://github.com/seamusabshere/upsert/issues/10
+
+1.1.0 / 2012-11-26
+
+* Enhancements
+
+  * Works on JRuby using bare-metal JDBC!
+  * Simplified.
+
+1.0.2 / 2012-11-12
+
+* Bug fixes
+
+  * Fix filenames - they were updated on an apparently case-insensitive setup. Thanks @ihough! (https://github.com/seamusabshere/upsert/pull/8)
+  * Deliberately drop MySQL procedures before creating them. Also thanks to @ihough!
+
+1.0.1 / 2012-11-07
+
+* Bug fixes
+
+  * Fix incorrect gem description
+
+1.0.0 / 2012-11-07
+
+* Breaking changes (well, not really)
+
+  * Not using INSERT ... ON DUPLICATE KEY UPDATE for MySQL!
+
+* Enhancements
+
+  * Replaced ON DUPLICATE KEY with a true merge function (procedure)
+  * Simplified code - buffering is no longer used anywhere
+  * Clarified documentation
+
+* Bug fixes
+
+  * MySQL upserts won't fail if you have a multi-key selector and no multi-column UNIQUE index to cover them (https://github.com/seamusabshere/upsert/issues/6)
+
+0.5.0 / 2012-09-21
+
+* Breaking changes (well, not really)
+
+  * "document" (as in the second argument to #row) has been renamed to "setter"!
+
+* Bug fixes
+
+  * If you say upsert({:name => 'Jerry', :color => 'red'}), make sure that it only affects rows really meeting those conditions
+  * Always sort selector and setter keys - i.e., column names - before doing anything with them
+  * Support PostgreSQL 9.1+
+  * Support MRI 1.8
+
+* Enhancements
+
+  * Slightly faster benchmarks for SQlite3 and MySQL
+  * Slightly slower on PostgreSQL (probably because the merge function requires more arguments), but more accurate
+  * Slightly clearer code structure
+  * Use bind parameters instead of quoting for PostgreSQL and SQLite3.
+  * Provide Upsert.clear_database_functions(connection) (currently only for PostgreSQL)
+  * Don't subclass String for Upset::Binary... hopefully save some strcpy()s?
+
+0.4.0 / 2012-09-04
+
+* Bug fixes
+
+  * Don't raise TooBig - rely on Mysql2 to complain about oversized packets
+
+* Enhancements
+
+  * Re-use PostgreSQL merge functions across connections, even outside of batch mode. Huzzah!
+  * For MySQL, increase speed for one-off upserts by not checking packet size
+  * Allow configuring Upsert.logger. Defaults to Rails.logger or Logger.new($stderr). If you set env var UPSERT_DEBUG=true then it will set log level to debug.
+
+0.3.4 / 2012-07-03
+
+* Bug fixes
+
+  * Allow upserting by auto-increment primary key (thanks @atandrau https://github.com/seamusabshere/upsert/issues/3)
+
+* Enhancements
+
+  * Make setter an optional argument
+
+0.3.3 / 2012-06-26
+
+* Bug fixes
+
+  * Properly quote table names - don't assume that everybody has ANSI_QUOTES turned on in MySQL :)
+
+0.3.2 / 2012-06-22
+
+* Enhancements
+
+  * Make sure ::PGconn is recognized as ::PG::Connection (thanks @joevandyk https://github.com/seamusabshere/upsert/issues/2)
+
+0.3.1 / 2012-06-21
+
+* Bug fixes
+
+  * On PostgreSQL, stop nullifying columns that weren't even involved in the upsert
+  * On SQLite, properly join WHERE conditions with ' AND ' instead of ','
+
+0.3.0 / 2012-06-21
+
+* Enhancements
+
+  * Remove all the sampling - just keep a cumulative total of sql bytes as we build up an ON DUPLICATE KEY UPDATE query.
+  * Deprecate Upsert.stream in favor of Upsert.batch (but provide an alias for backwards compat)
+
+0.2.2 / 2012-06-21
+
+* Bug fixes
+
+  * Correct and simplify how sql length is calculated when batching MySQL upserts.
+
+0.2.1 / 2012-06-21
+
+* Enhancements
+
+  * Added support for Ruby 1.8.7

data/Gemfile

@@ -0,0 +1,20 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in upsert.gemspec
+
+if Gem::Version.new(Bundler::VERSION) >= Gem::Version.new("2.0.0")
+  gemspec glob: RUBY_PLATFORM == "java" ? "upsert-java.gemspec" : "upsert.gemspec"
+else
+  gemspec name: RUBY_PLATFORM == "java" ? "upsert-java" : "upsert"
+end
+
+case RUBY_PLATFORM
+when "java"
+  gem "ffi", platforms: :jruby
+else
+  gem "ffi"
+end
+
+group "test" do
+  gem "testmetrics_rspec"
+end

data/LICENSE

@@ -0,0 +1,24 @@
+Copyright (c) 2013-2019 Seamus Abshere
+Copyright (c) 2017-2019 Philip Schalm
+Portions Copyright (c) 2019 The JRuby Team
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,411 @@
+# Upsert
+
+[![Build Status](https://travis-ci.org/seamusabshere/upsert.svg?branch=master)](https://travis-ci.org/seamusabshere/upsert)
+
+Make it easy to upsert on traditional RDBMS like MySQL, PostgreSQL, and SQLite3—hey look NoSQL!. Transparently creates (and re-uses) stored procedures/functions when necessary.
+
+You pass it a bare-metal connection to the database like `Mysql2::Client` (from `mysql2` gem on MRI) or `Java::OrgPostgresqlJdbc4::Jdbc4Connection` (from `jdbc-postgres` on Jruby).
+
+As databases start to natively support SQL MERGE (which is basically upsert), this library will take advantage (but you won't have to change your code).
+
+Does **not** depend on ActiveRecord.
+
+Does **not** use `INSERT ON DUPLICATE KEY UPDATE` on MySQL as this only works if you are very careful about creating unique indexes.
+
+70–90%+ faster than emulating upsert with ActiveRecord.
+
+Supports MRI and JRuby.
+
+## Usage
+
+You pass a __selector__ that uniquely identifies a row, whether it exists or not. You also pass a __setter__, attributes that should be set on that row.
+
+Syntax inspired by [mongo-ruby-driver's update method](http://api.mongodb.org/ruby/1.6.4/Mongo/Collection.html#update-instance_method).
+
+### Basic
+
+```ruby
+connection = Mysql2::Client.new([...])
+table_name = :pets
+upsert = Upsert.new connection, table_name
+# N times...
+upsert.row({:name => 'Jerry'}, :breed => 'beagle', :created_at => Time.now)
+```
+
+The `created_at` and `created_on` columns are used for inserts, but ignored on updates.
+
+So just to reiterate you've got a __selector__ and a __setter__:
+
+```ruby
+selector = { :name => 'Jerry' }
+setter = { :breed => 'beagle' }
+upsert.row(selector, setter)
+```
+
+### Batch mode
+
+By organizing your upserts into a batch, we can do work behind the scenes to make them faster.
+
+```ruby
+connection = Mysql2::Client.new([...])
+Upsert.batch(connection, :pets) do |upsert|
+  # N times...
+  upsert.row({:name => 'Jerry'}, :breed => 'beagle')
+  upsert.row({:name => 'Pierre'}, :breed => 'tabby')
+end
+```
+
+Batch mode is tested to be about 80% faster on PostgreSQL, MySQL, and SQLite3 than other ways to emulate upsert (see the tests, which fail if they are not faster).
+
+### Native Postgres upsert
+
+`INSERT ... ON CONFLICT DO UPDATE` is used when Postgres 9.5+ is detected and *unique constraint are in place.*
+
+**Note: ** You must have a **unique constraint** on the column(s) you're using as a selector.  A unique index won't work.  See https://github.com/seamusabshere/upsert/issues/98#issuecomment-295341405 for more information and some ways to check.
+
+If you don't have unique constraints, it will fall back to the classic Upsert gem user-defined function, which does not require a constraint.
+
+### ActiveRecord helper method
+
+```ruby
+require 'upsert/active_record_upsert'
+# N times...
+Pet.upsert({:name => 'Jerry'}, :breed => 'beagle')
+```
+
+## Wishlist
+
+Pull requests for any of these would be greatly appreciated:
+
+1. Cache JDBC PreparedStatement objects.
+1. Sanity check my three benchmarks (four if you include activerecord-import on MySQL). Do they accurately represent optimized alternatives?
+1. Provide `require 'upsert/debug'` that will make sure you are selecting on columns that have unique indexes
+1. Test that `Upsert` instances accept arbitrary columns, even within a batch, which is what people probably expect.
+1. [@antage](https://github.com/antage)'s idea for "true" upserting: (from https://github.com/seamusabshere/upsert/issues/17)
+
+```ruby
+selector = { id: 15 }
+update_setter = { count: Upsert.sql('count + 1') }
+insert_setter = { count: 1 }
+upsert.row_with_two_setter(update_setter, insert_setter, selector)
+```
+
+## Real-world usage
+
+<p><a href="http://angel.co/faraday"><img src="https://s3.amazonaws.com/photos.angel.co/startups/i/175701-a63ebd1b56a401e905963c64958204d4-medium_jpg.jpg" alt="Faraday logo"/></a></p>
+
+We use `upsert` for [big data at Faraday](http://angel.co/faraday). Originally written to speed up the [`data_miner`](https://github.com/seamusabshere/data_miner) data mining library.
+
+## Supported databases/drivers
+
+<table>
+  <tr>
+    <th>*</th>
+    <th>MySQL</th>
+    <th>PostgreSQL</th>
+    <th>SQLite3</th>
+  </tr>
+  <tr>
+    <th>MRI</th>
+    <td><a href="https://rubygems.org/gems/mysql2">mysql2</a></td>
+    <td><a href="https://rubygems.org/gems/pg">pg</a></td>
+    <td><a href="https://rubygems.org/gems/sqlite3">sqlite3</a></td>
+  </tr>
+  <tr>
+    <th>JRuby</th>
+    <td><a href="https://rubygems.org/gems/jdbc-mysql">jdbc-mysql</a></td>
+    <td><a href="https://rubygems.org/gems/jdbc-postgres">jdbc-postgres</a></td>
+    <td><a href="https://rubygems.org/gems/jdbc-sqlite3">jdbc-sqlite3</a></td>
+  </tr>
+</table>
+
+See below for details about what SQL MERGE trick (emulation of upsert) is used, performance, code examples, etc.
+
+### Rails / ActiveRecord
+
+(Assuming that one of the other three supported drivers is being used under the covers).
+
+* add "upsert" to your Gemfile and 
+* run bundle install
+
+```ruby
+Upsert.new Pet.connection, Pet.table_name
+```
+
+#### Speed
+
+Depends on the driver being used!
+
+#### SQL MERGE trick
+
+Depends on the driver being used!
+
+### MySQL
+
+On MRI, use the [mysql2](https://rubygems.org/gems/mysql2) driver.
+
+```ruby
+require 'mysql2'
+connection = Mysql2::Connection.new(:username => 'root', :password => 'password', :database => 'upsert_test')
+table_name = :pets
+upsert = Upsert.new(connection, table_name)
+```
+
+On JRuby, use the [jdbc-mysql](https://rubygems.org/gems/jdbc-mysql) driver.
+
+```ruby
+require 'jdbc/mysql'
+java.sql.DriverManager.register_driver com.mysql.jdbc.Driver.new
+connection = java.sql.DriverManager.get_connection "jdbc:mysql://127.0.0.1/mydatabase?user=root&password=password"
+```
+
+#### Speed
+
+From the tests (updated 11/7/12):
+
+    Upsert was 82% faster than find + new/set/save
+    Upsert was 85% faster than find_or_create + update_attributes
+    Upsert was 90% faster than create + rescue/find/update
+    Upsert was 46% faster than faking upserts with activerecord-import (note: in question as of 3/13/15, need some expert advice)
+
+#### SQL MERGE trick
+
+Thanks to [Dennis Hennen's StackOverflow response!](http://stackoverflow.com/questions/11371479/how-to-translate-postgresql-merge-db-aka-upsert-function-into-mysql/)!
+
+```sql
+CREATE PROCEDURE upsert_pets_SEL_name_A_tag_number_SET_name_A_tag_number(`name_sel` varchar(255), `tag_number_sel` int(11), `name_set` varchar(255), `tag_number_set` int(11))
+BEGIN
+  DECLARE done BOOLEAN;
+  REPEAT
+    BEGIN
+      -- If there is a unique key constraint error then
+      -- someone made a concurrent insert. Reset the sentinel
+      -- and try again.
+      DECLARE ER_DUP_UNIQUE CONDITION FOR 23000;
+      DECLARE ER_INTEG CONDITION FOR 1062;
+      DECLARE CONTINUE HANDLER FOR ER_DUP_UNIQUE BEGIN
+        SET done = FALSE;
+      END;
+
+      DECLARE CONTINUE HANDLER FOR ER_INTEG BEGIN
+        SET done = TRUE;
+      END;
+
+      SET done = TRUE;
+      SELECT COUNT(*) INTO @count FROM `pets` WHERE `name` = `name_sel` AND `tag_number` = `tag_number_sel`;
+      -- Race condition here. If a concurrent INSERT is made after
+      -- the SELECT but before the INSERT below we'll get a duplicate
+      -- key error. But the handler above will take care of that.
+      IF @count > 0 THEN
+        -- UPDATE table_name SET b = b_SET WHERE a = a_SEL;
+        UPDATE `pets` SET `name` = `name_set`, `tag_number` = `tag_number_set` WHERE `name` = `name_sel` AND `tag_number` = `tag_number_sel`;
+      ELSE
+        -- INSERT INTO table_name (a, b) VALUES (k, data);
+        INSERT INTO `pets` (`name`, `tag_number`) VALUES (`name_set`, `tag_number_set`);
+      END IF;
+    END;
+  UNTIL done END REPEAT;
+END
+```
+
+### PostgreSQL
+
+On MRI, use the [pg](https://rubygems.org/gems/pg) driver.
+
+```ruby
+require 'pg'
+connection = PG.connect(:dbname => 'upsert_test')
+table_name = :pets
+upsert = Upsert.new(connection, table_name)
+```
+
+On JRuby, use the [jdbc-postgres](https://rubygems.org/gems/jdbc-postgres) driver.
+
+```ruby
+require 'jdbc/postgres'
+java.sql.DriverManager.register_driver org.postgresql.Driver.new
+connection = java.sql.DriverManager.get_connection "jdbc:postgresql://127.0.0.1/mydatabase?user=root&password=password"
+```
+
+If you want to use HStore, make the `pg-hstore` gem available and pass a Hash in setters:
+
+```ruby
+gem 'pg-hstore'
+require 'pg_hstore'
+upsert.row({:name => 'Bill'}, :mydata => {:a => 1, :b => 2})
+```
+
+#### PostgreSQL notes
+
+- Upsert doesn't do any type casting, so if you attempt to do something like the following:
+    `upsert.row({ :name => 'A Name' }, :tag_number => 'bob')`
+    you'll get an error which reads something like:
+    `invalid input syntax for integer: "bob"`
+
+
+
+#### Speed
+
+From the tests (updated 9/21/12):
+
+    Upsert was 72% faster than find + new/set/save
+    Upsert was 79% faster than find_or_create + update_attributes
+    Upsert was 83% faster than create + rescue/find/update
+    # (can't compare to activerecord-import because you can't fake it on pg)
+
+#### SQL MERGE trick
+
+Adapted from the [canonical PostgreSQL upsert example](http://www.postgresql.org/docs/current/interactive/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING):
+
+```sql
+CREATE OR REPLACE FUNCTION upsert_pets_SEL_name_A_tag_number_SET_name_A_tag_number("name_sel" character varying(255), "tag_number_sel" integer, "name_set" character varying(255), "tag_number_set" integer) RETURNS VOID AS
+$$
+DECLARE
+  first_try INTEGER := 1;
+BEGIN
+  LOOP
+    -- first try to update the key
+    UPDATE "pets" SET "name" = "name_set", "tag_number" = "tag_number_set"
+      WHERE "name" = "name_sel" AND "tag_number" = "tag_number_sel";
+    IF found THEN
+      RETURN;
+    END IF;
+    -- not there, so try to insert the key
+    -- if someone else inserts the same key concurrently,
+    -- we could get a unique-key failure
+    BEGIN
+      INSERT INTO "pets"("name", "tag_number") VALUES ("name_set", "tag_number_set");
+      RETURN;
+    EXCEPTION WHEN unique_violation THEN
+      -- seamusabshere 9/20/12 only retry once
+      IF (first_try = 1) THEN
+        first_try := 0;
+      ELSE
+        RETURN;
+      END IF;
+      -- Do nothing, and loop to try the UPDATE again.
+    END;
+  END LOOP;
+END;
+$$
+LANGUAGE plpgsql;
+```
+
+I slightly modified it so that it only retries once - don't want infinite loops.
+
+### Sqlite
+
+On MRI, use the [sqlite3](https://rubygems.org/gems/sqlite3) driver.
+
+```ruby
+require 'sqlite3'
+connection = SQLite3::Database.open(':memory:')
+table_name = :pets
+upsert = Upsert.new(connection, table_name)
+```
+
+On JRuby, use the [jdbc-sqlite3](https://rubygems.org/gems/jdbc-sqlite3) driver.
+
+```ruby
+# TODO somebody please verify
+require 'jdbc/sqlite3'
+java.sql.DriverManager.register_driver org.sqlite.Driver.new
+connection = java.sql.DriverManager.get_connection "jdbc:sqlite://127.0.0.1/mydatabase?user=root&password=password"
+```
+
+#### Speed
+
+From the tests (updated 9/21/12):
+
+    Upsert was 77% faster than find + new/set/save
+    Upsert was 80% faster than find_or_create + update_attributes
+    Upsert was 85% faster than create + rescue/find/update
+    # (can't compare to activerecord-import because you can't fake it on sqlite3)
+
+#### SQL MERGE trick
+
+Thanks to [@dan04's answer on StackOverflow](http://stackoverflow.com/questions/2717590/sqlite-upsert-on-duplicate-key-update):
+
+**Please note!  This will only work properly on Sqlite if one of the columns being used as the "selector" are a primary key or unique index**
+
+```sql
+INSERT OR IGNORE INTO visits VALUES (127.0.0.1, 1);
+UPDATE visits SET visits = 1 WHERE ip LIKE 127.0.0.1;
+```
+
+## Features
+
+### Tested to be fast and portable
+
+In addition to correctness, the library's tests check that it is
+
+1. Faster than comparable upsert techniques
+2. Compatible with supported databases
+
+### Not dependent on ActiveRecord
+
+As below, all you need is a raw database connection like a `Mysql2::Connection`, `PG::Connection` or a `SQLite3::Database`. These are equivalent:
+
+```ruby
+# with activerecord
+Upsert.new ActiveRecord::Base.connection, :pets
+# with activerecord, prettier
+Upsert.new Pet.connection, Pet.table_name
+# without activerecord
+Upsert.new Mysql2::Connection.new([...]), :pets
+```
+
+### For a specific use case, faster and more portable than `activerecord-import`
+
+You could also use [activerecord-import](https://github.com/zdennis/activerecord-import) to upsert:
+
+```ruby
+Pet.import columns, all_values, :timestamps => false, :on_duplicate_key_update => columns
+```
+
+`activerecord-import`, however, only works on MySQL and requires ActiveRecord&mdash;and if all you are doing is upserts, `upsert` is tested to be 40% faster. And you don't have to put all of the rows to be upserted into a single huge array - you can batch them using `Upsert.batch`.
+
+## Gotchas
+
+### No automatic typecasting beyond what the adapter/driver provides
+
+We don't have any logic to convert integers into strings, strings into integers, etc. in order to satisfy PostgreSQL/etc.'s strictness on this issue.
+
+So if you try to upsert a blank string (`''`) into an integer field in PostgreSQL, you will get an error.
+
+### Dates and times are converted to UTC
+
+Datetimes are immediately converted to UTC and sent to the database as ISO8601 strings.
+
+If you're using MySQL, make sure server/connection timezone is UTC. If you're using Rails and/or ActiveRecord, you might want to check `ActiveRecord::Base.default_timezone`... it should probably be `:utc`.
+
+In general, run some upserts and make sure datetimes get persisted like you expect.
+
+### Clearning all library-generated functions
+
+Place the following in to a rake task (so you don't globally redefine the `NAME_PREFIX` constant)
+
+```ruby
+Upsert::MergeFunction::NAME_PREFIX = "upsert"
+
+# ActiveRecord
+Upsert.clear_database_functions(ActiveRecord::Base.connection)
+
+# Sequel
+DB.synchronize do |conn|
+  Upsert.clear_database_functions(conn)
+end
+```
+
+### Doesn't work with transactional fixtures
+
+Per https://github.com/seamusabshere/upsert/issues/23 you might have issues if you try to use transactional fixtures and this library.
+
+##
+Testmetrics - https://www.testmetrics.app/seamusabshere/upsert
+
+## Copyright
+
+Copyright 2013-2019 Seamus Abshere
+Copyright 2017-2019 Philip Schalm
+Portions Copyright (c) 2019 The JRuby Team