Project

General

Profile

Bug #12723

Getting constraint errors when updating jobs frequently

Added by Marc Mengel over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
05/19/2016
Due date:
% Done:

100%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

When we have shorter test jobs, we're getting constraint errors on the job history tables.

May be do to SQLAcchemy ORM flush() calls(?).

History

#1 Updated by Marc Mengel over 4 years ago

Some changes on the server side may be sufficient; I updated it to flush
particular objects so we don't re-flush the job without updating its timestamp(?).

4243cd52e83d0efed0af269eed2f9dea6381c759

but Steve is thinking about it, too.

#2 Updated by Marc Mengel over 4 years ago

  • Target version set to b0_5

#3 Updated by Marc Mengel over 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Since reworking update_job for the umpteenth time, this hasn't reoccurred. Not sure if Steven changed anything on the db side as well, but stopped doing flush() calls to get job_file_id's etc. and just added items to associations and did one commit at the end seems to have cleared this up.

#4 Updated by Marc Mengel over 4 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF