Postgres throws error when running import from activerecord-import gem

Question

I switched to Postgres in development and now following error breaks a test case:

PG::Error: ERROR:  column "id" of relation "assets_content_nodes" does not exist
:           SELECT pg_get_serial_sequence($1, $2)

Same error happens in development and production environments but it is not a show stopper and does not affect the import. assets_content_nodes is a join table and I'd rather not add the 'id' column. Any ideas why this may be happening?

Jim Stewart · Accepted Answer · 2013-03-01 17:00:23Z

1

This is fixed in activerecord-import -v0.3.1 (or possibly an earlier version, but it was broken in 0.2.11 and earlier). You no longer need an id column on a table to do an import.

answered Mar 1, 2013 at 17:00

Jim Stewart

17.4k5 gold badges77 silver badges91 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Seamus Abshere · Accepted Answer · 2013-03-01 17:42:43Z

0

You might also try Upsert.

If you're importing pets:

require 'csv'
require 'upsert'
u = Upsert.new Pet.connection, Pet.table_name
CSV.foreach('pets.csv', headers: :first_row) do |row|
  selector = { name: row['name'] }
  setter = row
  u.row selector, setter
end

My tests show it's 20–30% faster than activerecord-import. Since it's "upserting," it's generally OK if the process gets interrupted and you just start over from the beginning.

answered Mar 1, 2013 at 17:42

Seamus Abshere

8,5264 gold badges49 silver badges61 bronze badges

Collectives™ on Stack Overflow

Postgres throws error when running import from activerecord-import gem

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related