services/caches/search/all: last_modified should get modified on log entries

[opencaching]

services/caches/search/all: last_modified should get modified on log entries

[GoogleCodeExporter]

I think this would require a new column on the caches table. , I won't 
implement this until such column exists, for performance reasons.

Original comment by rygielski on 26 Aug 2011 at 9:48

[GoogleCodeExporter]

log.php need modified to add this entry i caches table but what we do when user 
(owner cache or owner log) delete last log entry by removelog.php

Original comment by sp2ong on 26 Aug 2011 at 10:00

[GoogleCodeExporter]

"logged_since" is a bad name for it, maybe "logs_changed_since" would be better.

I think developer wants to know when logs had changed in general, he doesn't 
care when the last log was submitted. Then, when user deleted a log entry, 
"logs_changed_since" would bump up to the current time.

Original comment by rygielski on 26 Aug 2011 at 10:37

[GoogleCodeExporter]

Original comment by rygielski on 26 Aug 2011 at 10:38

• Changed title: Add a "logs_changed_since" argument for services/caches/search/all method.

[GoogleCodeExporter]

Also, this functionality could be incorporated into an already existing column 
- the last_modified column. I think a "changed log" event may count as a "cache 
modification". Some developers would want this cache refreshed upon such events.

Original comment by rygielski on 26 Aug 2011 at 10:43

[GoogleCodeExporter]

When we talking about possible applications using OKAPI to sync OC database 
with local offline copy, all changes ( including new/modified logs ) should be 
taken into account.

Original comment by miklobit on 26 Aug 2011 at 11:39

[GoogleCodeExporter]

I wouldn't encourage developers to download our entire database. OKAPI
is meant primarilly as a tool for online access. If developers want to
have dumps of data for offline use, I think we should think of a
special method for that - it would return a static JSON/XML/SQL dump,
generated once a day.

Original comment by rygielski on 27 Aug 2011 at 9:27

[GoogleCodeExporter]

Original comment by rygielski on 29 Aug 2011 at 10:36

• Changed state: Blocked

[GoogleCodeExporter]

Original comment by rygielski on 1 Sep 2011 at 7:27

• Changed title: services/caches/search/all: last_modified should get modified on log entries

[GoogleCodeExporter]

The best solution I can think of:

Add two things to OKAPI db-update chain:
- Add a column "really_last_modified" of MySQL type "timestamp" to table 
"caches". Columns of "timestamp" type get automatically updated when anything 
in a row changes.
- Update existing "really_last_modified" columns based on caches.last_modified 
AND cache_logs.last_modified.

Original comment by rygielski on 1 Sep 2011 at 7:30

[GoogleCodeExporter]

Update: Added a new module 'replicate' to OKAPI. Now external developers may 
keep their database in sync with ours. This is somewhat relevant to this issue.

Original comment by rygielski on 12 Mar 2012 at 1:42

[GoogleCodeExporter]

It appears we won't be changing this. "last_modified" will still be modified 
ONLY when the owner of the cache OR system administrator changes something 
significant. It will NOT change in cases such as log entry.

BUT additional field to the database was added (caches.okapi_syncbase) which IS 
updated every time ANYTHING is changed in the row (i.e. after adding a log 
entry). We MAY think about using this field in conjunction with 
'modified_since' parameter IF some developer think they could use it. However, 
I assume that these developers will be much happier in using 'replicate' module 
instead. That's why I close this issue. If anyone thinks it necessary, please 
reopen.

Original comment by rygielski on 13 Apr 2012 at 9:17

• Changed state: WontFix