postgres-copy 0.5.7 → 0.5.8

data/Gemfile

@@ -1,4 +1,4 @@
-source :gemcutter
+source 'https://rubygems.org'
 
 # specify gem dependencies in activerecord-postgres-hstore.gemspec
 # except the platform-specific dependencies below

data/Gemfile.lock

@@ -1,41 +1,41 @@
 PATH
   remote: .
   specs:
-    postgres-copy (0.5.7)
+    postgres-copy (0.5.8)
       activerecord (>= 3.0.0)
       pg
       rails (>= 3.0.0)
       responders
 
 GEM
-  remote: http://rubygems.org/
+  remote: https://rubygems.org/
   specs:
-    actionmailer (3.2.11)
-      actionpack (= 3.2.11)
-      mail (~> 2.4.4)
-    actionpack (3.2.11)
-      activemodel (= 3.2.11)
-      activesupport (= 3.2.11)
+    actionmailer (3.2.13)
+      actionpack (= 3.2.13)
+      mail (~> 2.5.3)
+    actionpack (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
       builder (~> 3.0.0)
       erubis (~> 2.7.0)
       journey (~> 1.0.4)
-      rack (~> 1.4.0)
+      rack (~> 1.4.5)
       rack-cache (~> 1.2)
       rack-test (~> 0.6.1)
       sprockets (~> 2.2.1)
-    activemodel (3.2.11)
-      activesupport (= 3.2.11)
+    activemodel (3.2.13)
+      activesupport (= 3.2.13)
       builder (~> 3.0.0)
-    activerecord (3.2.11)
-      activemodel (= 3.2.11)
-      activesupport (= 3.2.11)
+    activerecord (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
       arel (~> 3.0.2)
       tzinfo (~> 0.3.29)
-    activeresource (3.2.11)
-      activemodel (= 3.2.11)
-      activesupport (= 3.2.11)
-    activesupport (3.2.11)
-      i18n (~> 0.6)
+    activeresource (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
+    activesupport (3.2.13)
+      i18n (= 0.6.1)
       multi_json (~> 1.0)
     arel (3.0.2)
     builder (3.0.4)
@@ -45,37 +45,37 @@ GEM
     i18n (0.6.1)
     journey (1.0.4)
     json (1.7.6)
-    mail (2.4.4)
+    mail (2.5.3)
       i18n (>= 0.4.0)
       mime-types (~> 1.16)
       treetop (~> 1.4.8)
-    mime-types (1.19)
-    multi_json (1.5.0)
-    pg (0.14.1)
+    mime-types (1.22)
+    multi_json (1.7.2)
+    pg (0.15.0)
     polyglot (0.3.3)
-    rack (1.4.4)
+    rack (1.4.5)
     rack-cache (1.2)
       rack (>= 0.4)
     rack-ssl (1.3.3)
       rack
     rack-test (0.6.2)
       rack (>= 1.0)
-    rails (3.2.11)
-      actionmailer (= 3.2.11)
-      actionpack (= 3.2.11)
-      activerecord (= 3.2.11)
-      activeresource (= 3.2.11)
-      activesupport (= 3.2.11)
+    rails (3.2.13)
+      actionmailer (= 3.2.13)
+      actionpack (= 3.2.13)
+      activerecord (= 3.2.13)
+      activeresource (= 3.2.13)
+      activesupport (= 3.2.13)
       bundler (~> 1.0)
-      railties (= 3.2.11)
-    railties (3.2.11)
-      actionpack (= 3.2.11)
-      activesupport (= 3.2.11)
+      railties (= 3.2.13)
+    railties (3.2.13)
+      actionpack (= 3.2.13)
+      activesupport (= 3.2.13)
       rack-ssl (~> 1.3.2)
       rake (>= 0.8.7)
       rdoc (~> 3.4)
       thor (>= 0.14.6, < 2.0)
-    rake (10.0.3)
+    rake (10.0.4)
     rdoc (3.12)
       json (~> 1.4)
     responders (0.9.3)
@@ -93,12 +93,12 @@ GEM
       multi_json (~> 1.0)
       rack (~> 1.0)
       tilt (~> 1.1, != 1.3.0)
-    thor (0.17.0)
-    tilt (1.3.3)
+    thor (0.18.1)
+    tilt (1.3.6)
     treetop (1.4.12)
       polyglot
       polyglot (>= 0.3.1)
-    tzinfo (0.3.35)
+    tzinfo (0.3.37)
 
 PLATFORMS
   ruby

data/README.md

@@ -1,4 +1,4 @@
-# postgres-copy
+# postgres-copy [![Build Status](https://travis-ci.org/diogob/postgres-copy.png?branch=master)](https://travis-ci.org/diogob/postgres-copy)
 
 This Gem will enable your AR models to use the PostgreSQL COPY command to import/export data in CSV format.
 If you need to tranfer data between a PostgreSQL database and CSV files, the PostgreSQL native CSV parser
@@ -32,47 +32,65 @@ You can go to the rails console and try some cool things first.
 The first and most basic use case, let's copy the enteire content of a database table to a CSV file on the database server disk.
 Assuming we have a users table and a User AR model:
 
-    User.pg_copy_to '/tmp/users.csv'
+```ruby
+User.pg_copy_to '/tmp/users.csv'
+```
 
 This will execute in the database the command:
 
-    COPY (SELECT "users".* FROM "users" ) TO '/tmp/users.csv' WITH DELIMITER ',' CSV HEADER
+```sql
+COPY (SELECT "users".* FROM "users" ) TO '/tmp/users.csv' WITH DELIMITER ',' CSV HEADER
+```
 
 Remark that the file will be created in the database server disk.  
 But what if you want to write the lines in a file on the server that is running Rails, instead of the database?  
 In this case you can pass a block and retrieve the generated lines and then write them to a file:
 
-    File.open('/tmp/users.csv', 'w') do |f|
-      User.pg_copy_to do |line|
-        f.write line
-      end
-    end
+```ruby
+File.open('/tmp/users.csv', 'w') do |f|
+  User.pg_copy_to do |line|
+    f.write line
+  end
+end
+```
 
 Or, if you have enough memory, you can read all table contents to a string using .pg_copy_to_string
 
-    puts User.pg_copy_to_string
+```ruby
+puts User.pg_copy_to_string
+```
 
 Another insteresting feature of pg_copy_to is that it uses the scoped relation, it means that you can use ARel 
 operations to generate different CSV files according to your needs.
 Assuming we want to generate a file only with the names of users 1, 2 and 3:
 
-    User.select("name").where(:id => [1,2,3]).pg_copy_to "/tmp/users.csv"
+```ruby
+User.select("name").where(:id => [1,2,3]).pg_copy_to "/tmp/users.csv"
+```
 
 Which will generate the following SQL command:
 
-    COPY (SELECT name FROM "users" WHERE "users"."id" IN (1, 2, 3)) TO '/tmp/users.csv' WITH DELIMITER ',' CSV HEADER
+```sql
+COPY (SELECT name FROM "users" WHERE "users"."id" IN (1, 2, 3)) TO '/tmp/users.csv' WITH DELIMITER ',' CSV HEADER
+```
 
 The COPY command also supports exporting the data in binary format.
 
-    User.select("name").where(:id => [1,2,3]).pg_copy_to "/tmp/users.dat", :format => :binary
+```ruby
+User.select("name").where(:id => [1,2,3]).pg_copy_to "/tmp/users.dat", :format => :binary
+```
 
 Which will generate the following SQL command:
 
-    COPY (SELECT name FROM "users" WHERE "users"."id" IN (1, 2, 3)) TO '/tmp/users.dat' WITH BINARY
+```sql
+COPY (SELECT name FROM "users" WHERE "users"."id" IN (1, 2, 3)) TO '/tmp/users.dat' WITH BINARY
+```
 
 The copy_to_string method also supports this
 
-    puts User.pg_copy_to_string(:format => :binary)
+```ruby
+puts User.pg_copy_to_string(:format => :binary)
+```
 
 
 
@@ -83,19 +101,25 @@ It will allow you to copy data from an arbritary IO object or from a file in the
 Let's first copy from a file in the database server, assuming again that we have a users table and
 that we are in the Rails console:
 
-    User.pg_copy_from "/tmp/users.csv"
+```ruby
+User.pg_copy_from "/tmp/users.csv"
+```
 
 This command will use the headers in the CSV file as fields of the target table, so beware to always have a header in the files you want to import.
 If the column names in the CSV header do not match the field names of the target table, you can pass a map in the options parameter.
 
-    User.pg_copy_from "/tmp/users.csv", :map => {'name' => 'first_name'}
+```ruby
+User.pg_copy_from "/tmp/users.csv", :map => {'name' => 'first_name'}
+```
 
 In the above example the header name in the CSV file will be mapped to the field called first_name in the users table.
 You can also manipulate and modify the values of the file being imported before they enter into the database using a block:
 
-    User.pg_copy_from "/tmp/users.csv" do |row|
-      row[0] = "fixed string"
-    end
+```ruby
+User.pg_copy_from "/tmp/users.csv" do |row|
+  row[0] = "fixed string"
+end
+```
 
 The above extample will always change the value of the first column to "fixed string" before storing it into the database.
 For each iteration of the block row receives an array with the same order as the columns in the CSV file.
@@ -103,17 +127,23 @@ For each iteration of the block row receives an array with the same order as the
 
 To copy a binary formatted data file or IO object you can specify the format as binary
 
-    User.pg_copy_from "/tmp/users.dat", :format => :binary
+```ruby
+User.pg_copy_from "/tmp/users.dat", :format => :binary
+```
 
 NOTE: Columns must line up with the table unless you specify how they map to table columns.
 
 To specify how the columns will map to the table you can specify the :columns option
 
-    User.pg_copy_from "/tmp/users.dat", :format => :binary, :columns => [:id, :name]
+```ruby
+User.pg_copy_from "/tmp/users.dat", :format => :binary, :columns => [:id, :name]
+```
 
 Which will generate the following SQL command:
 
-    COPY users (id, name) FROM '/tmp/users.dat' WITH BINARY
+```sql
+COPY users (id, name) FROM '/tmp/users.dat' WITH BINARY
+```
 
 
 ### Using the CSV Responder

data/lib/postgres-copy/active_record.rb

@@ -24,7 +24,7 @@ module ActiveRecord
     # Copy all data to a single string
     def self.pg_copy_to_string options = {}
       data = ''
-      self.pg_copy_to(nil, options){|l| data += l }
+      self.pg_copy_to(nil, options){|l| data << l }
       if options[:format] == :binary
         data.force_encoding("ASCII-8BIT")
       end

data/postgres-copy.gemspec

@@ -5,7 +5,7 @@ $:.unshift lib unless $:.include?(lib)
 
 Gem::Specification.new do |s|
   s.name = "postgres-copy"
-  s.version = "0.5.7"
+  s.version = "0.5.8"
 
   s.platform    = Gem::Platform::RUBY
   s.required_ruby_version     = ">= 1.8.7"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: postgres-copy
 version: !ruby/object:Gem::Version
-  version: 0.5.7
+  version: 0.5.8
   prerelease: 
 platform: ruby
 authors:
@@ -184,10 +184,10 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -2280961543461931489
+      hash: 489106335970440028
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.24
+rubygems_version: 1.8.25
 signing_key: 
 specification_version: 3
 summary: Put COPY command functionality in ActiveRecord's model class