diff options
author | Thomas Lange <code@nerdmind.de> | 2017-05-21 07:37:58 +0200 |
---|---|---|
committer | Thomas Lange <code@nerdmind.de> | 2017-05-21 07:55:27 +0200 |
commit | 1f1de386b09e48a02fccd62aa82ff319533969cc (patch) | |
tree | ac3d610bafcb1ebdd23ee56db23c59377aaee0fc /system/page | |
parent | eeddde7ae72d7f68c0a734d1fe7004cde847d1e5 (diff) | |
download | blog-1f1de386b09e48a02fccd62aa82ff319533969cc.tar.gz blog-1f1de386b09e48a02fccd62aa82ff319533969cc.tar.xz blog-1f1de386b09e48a02fccd62aa82ff319533969cc.zip |
Bugfixes: There were two problems with the internal sorting of items which have been fixed. This results in version 2.1.2 (database update recommended):v2.1.2
+ Bugfix [core]: If the insertion date of a newly created item has been placed to a datetime in the past after which other items have already appeared, the sorting of the forward and backward functionality has been interrupted because the WHERE clause in the database query had the condition that the next item must have a higher ID and the previous item must have a lower ID than the current one. If this newly created item was the last one and the insertion date had been placed to a datetime in the past, no next item could be fetched because THIS is already the item with the highest ID and the correct sorting by time_insert for this item has stopped working.
+ Bugfix [core]: If one or more items had exactly the same insertion time, the items with the exact same time has been appeard within the overview list in an order which did not correspond to the insertion sequence. There were several ways to fix this problem, but this would result in more complicated database queries and more code. To fix the problem in the simplest way, the column "time_insert" now has a UNIQUE index to prevent two or more items from having the exactly same insertion time.
Database update to version 2.1.2 (no existing data will be lost or changed):
ALTER TABLE `page` ADD UNIQUE KEY `time_insert` (`time_insert`);
ALTER TABLE `post` ADD UNIQUE KEY `time_insert` (`time_insert`);
ALTER TABLE `user` ADD UNIQUE KEY `time_insert` (`time_insert`);
Diffstat (limited to 'system/page')
0 files changed, 0 insertions, 0 deletions