lots of PG::UniqueViolation: "duplicate key value violates unique constraint" errors

[bteitelb]

I see lots of exceptions like this for: activities, users, workshops, and possibly other tables. What's going on?

[bteitelb]

I deployed the potential fix to #43. If that works, we'll have more informative exceptions which could shed some light on why we are violating Postgres's constraints.

[bteitelb]

It looks like all of the failures are on the primary keys. So, we may need to reset Postgres's primary key sequences, as described here: http://stackoverflow.com/questions/244243/how-to-reset-postgres-primary-key-sequence-when-it-falls-out-of-sync

[antmachine]

Reset the keys. I set the nextval to be 1 higher than current maxval on all of the tables where the primary key was out of sync. Not sure how that happened...