Project

General

Profile

Actions

Bug #5383

closed

[API] API server should always retrieve current time from database, never Time.now()

Added by Tom Clegg over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Radhika Chippada
Category:
API
Target version:
Story points:
0.5

Description

If possible, the created_at and modified_at timestamps should be set by putting CURRENT_TIMESTAMP() in the SQL statement, rather than calling CURRENT_TIMESTAMP() and sending the value in a subsequent INSERT or UPDATE. This lets us rely on those timestamps to indicate the order in which database modifications actually happened.


Subtasks 2 (0 open2 closed)

Task #5450: Add test case for looking up a record by created_at, using the exact timestamp given in a #create response.ResolvedRadhika Chippada03/16/2015Actions
Task #5472: Review branch: 5383-api-db-current-timeResolvedRadhika Chippada03/16/2015Actions

Related issues

Related to Arvados - Bug #5381: [Crunch] Node went away unexpectedly during pipeline run.ClosedActions
Actions

Also available in: Atom PDF