Project

General

Profile

Bug #3753

modified_date updated but not showing as greatest date

Added by Kyle Hazelwood over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Urgent
Category:
Database
Target version:
-
Start date:
04/23/2013
Due date:
% Done:

0%

Estimated time:
Duration:

Description

The modified_date column of entries table had been updated but when trying to find the greatest/max date between creation_date and modified_date the old date was appearing. This caused the dbcache to never poll for newly edited entries. To see the edited entry correctly you had to change the date index/span. I believe this may be related to a syntax error the editEntry method had that kept it from finishing the transaction. For a while the db was hung on this transaction that never finished, this stopped without any intervention but the above problem began after that time. If I had to guess, I would say that the modified_date_update() function was locked by the unfinished transaction somehow.

History

#1 Updated by Kyle Hazelwood over 7 years ago

  • Subject changed from modified_date updated but not showing as max date to modified_date updated but not showing as greatest date
  • Category set to Database
  • Status changed from New to Closed

I'm unsure was the true failure was but rebuilding all the tables fixed it. The editEntry method has been fixed and everything appears to work again.

#2 Updated by Kyle Hazelwood over 7 years ago

  • Status changed from Closed to Assigned
  • Assignee set to Kyle Hazelwood
  • Priority changed from Normal to Urgent

Issue popped back up! Something must not work with the maxDate... methods. The date returned is always equal to the first entry edited. The only way the entries dbCache gets updated is when the entryIDs change.

#3 Updated by Kyle Hazelwood over 7 years ago

  • Status changed from Assigned to Closed

Fixed it by changing db function to MAX from GREATEST. Thats what I orginally had in sybase, why did I change it?



Also available in: Atom PDF