Duplicate key error for Records

[spacemansteve]

The error is on the Records table, not ChangeLog as previously thought.
The log file shows:

/usr/local/lib/python2.7/dist-packages/celery/app/trace.py:549: RuntimeWarning: 
Exception raised outside body: 
Retry(Retry(...), IntegrityError('(psycopg2.IntegrityError) 
duplicate key value violates unique constraint 
\"records_bibcode_key\"\\nDETAIL:  Key (bibcode)=(2014arXiv1409.3409Z) already exists.

In Postgres, the key field has a primary key constrain. It is visible with: select * from information_schema.table_constraints where table_name='change_log'.

This does not appear to come from the model definition.

In app.py, ChangeLog entries are added with a simple append operation.

[romanchyla]

that's a mistake; either there should be no primary key; or a secondary key in combination with some other (but which field, i dunno - key will eventually result in duplicates; date doesn't make much sense - or does it?)

[spacemansteve]

ChangeLog table includes an id field that could serve as the primary key.

[romanchyla]

the id should be the primary; i think the key was only meant to be indexed

[spacemansteve]

We are no losing any data due to these errors.