[Tickets #12558] Re: History: Add getLatestEntry($guid)

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12558
------------------------------------------------------------------------------
  Ticket             | 12558
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | History: Add getLatestEntry($guid)
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Enhancement
-State              | Feedback
+State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Michael Rubinsky
+New Attachment     |  
v2-0001-Add-getLatestEntry-guid-to-get-the-latest-history-en.patch
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-08-21 09:13) wrote:

I've updated the code with the optimized SQL statement using ORDER BY.

Also I've fixed a bug that only occurred during productive testing:
If db->selectOne() didn't find a row, it returned an array with
all the requested keys set and empty values. Could be related to the  
MAX() statement
and/or the explicit specification of the field names in the previous  
SQL statement.

Therefore I've adapted the code to check if $row['history_id'] is really set.
No unit test yet, productive testing has to do for now :o)




Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-08-21 09:13)  
uploaded:  
v2-0001-Add-getLatestEntry-guid-to-get-the-latest-history-en.patch

http://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=v2-0001-Add-getLatestEntry-guid-to-get-the-latest-history-en.patch&ticket=12558&fn=%2Fv2-0001-Add-getLatestEntry-guid-to-get-the-latest-history-en.patch