XML interface and rating fixes and changes; updates #244

- XML interface update to v1.4
-- added listing_last_modified and log_last_modified fields
-- changed and fixed handling of ratings for multiple found logs of one user
-- resend log records after editing (only) rating or withdrawing rating via mytop5
-- logtype fix: convert type > 8 to 3 in XML versions < 1.3

- fixed rating handling when deleting one of multiple found logs
-- added dbmaintain update procedure for this fix
- show only one rating star when a user logged multiple founds
- added trigger update function to database versioning
This commit is contained in:
following
2013-06-23 20:45:43 +02:00
parent 373e922c8d
commit 371894d177
13 changed files with 363 additions and 35 deletions

View File

@@ -44,6 +44,20 @@
} while ($db_version > 0);
// Now and then a maintain.php update should be inserted, because multiple
// mutations may be run in one batch, and future mutations may depend on
// changed triggers, which may not be obvious.
// Of course, a trigger update mutation can also be inserted directly before a
// mutation which needs it. (But take care that maintain.php at that point does
// not depend on database changes which will be done by that mutation ...)
function update_triggers()
{
global $opt;
system('php ' . $opt['rootpath'] . 'doc/sql/stored-proc/maintain.php');
}
// Database mutations
// - must be consecutively numbered
// - should behave well if run multiple times
@@ -246,4 +260,9 @@
sql("ALTER TABLE `caches` ADD INDEX `wp_gc_maintained` (`wp_gc_maintained`)");
}
function dbv_113() // preventive trigger update
{
update_triggers();
}
?>