← Back to team overview

dhis2-devs team mailing list archive

Re: Weird cache issue

 

Halvdan,

Ah, OK, and not - I was not using any queries, I simply updated the Data
Set names directly in the table.

As I've said - the weird thing is that all those new names immediately
showed up in the UI data set list, but the old names are still appearing
wherever the Data Integrity process throws up integrity violations

Regards
Calle

On 1 September 2015 at 18:01, Halvdan Grelland <halvdanhg@xxxxxxxxx> wrote:

> Calle, I'm pretty sure Jason was referring to whatever you were doing to
> update the records (your point #1 in original email) which was not, as far
> as I can understand, using the UI or the web-api. I am not familiar with
> "pgremote" but am assuming it's some kind of postgres connector allowing
> you to run (sql) queries. We'd need to see those queries in order to figure
> out what could have gone wrong.
>
> 2015-09-01 14:50 GMT+02:00 Calle Hedberg <calle.hedberg@xxxxxxxxx>:
>
>> Jason
>>
>> I was not executing any custom sql - I'm running the Data Administration
>> -> Data Integrity process checks.
>>
>> My reference to the sql queries being run relates to my ASSUMPTION that
>> the Data Integrity checks are a series of SQL queries - but maybe not,
>> maybe the integrity checks are a series of web api calls followed by some
>> kind of front-end processing? I just don't know, and I'm not a Java
>> developer and I don't have the code base on my laptop so I cannot find out
>> myself...
>>
>> Seems my initial post was not clear enough on this - apologies for that.
>>
>> Regards
>> Calle
>>
>> On 1 September 2015 at 14:31, Jason Pickering <
>> jason.p.pickering@xxxxxxxxx> wrote:
>>
>>> Hi Calle,
>>> It is very difficult to say much without knowing what SQL it was you
>>> executed. In general, use of the API or UI is usually much safer.
>>>
>>> Do you have any sort of cache in front of your DHIS2 instance?
>>>
>>> Can you confirm from the database that the names were actually changed?
>>>
>>> Regards,
>>> Jason
>>>
>>>
>>> On Tue, Sep 1, 2015 at 12:49 PM, Calle Hedberg <calle.hedberg@xxxxxxxxx>
>>> wrote:
>>>
>>>> Lars,
>>>>
>>>> Nope - all data set names and short names are the same.
>>>>
>>>> It's just weird, and I don't like inexplicable things happening to a
>>>> database....
>>>>
>>>> When you run data integrity - WHERE are those queries fetching data
>>>> from? Are the integrity queries running against the database itself, or
>>>> some kind of cache repository?
>>>>
>>>> Regards
>>>> Calle
>>>>
>>>> On 1 September 2015 at 13:00, Lars Helge Øverland <larshelge@xxxxxxxxx>
>>>> wrote:
>>>>
>>>>> Hi Calle,
>>>>>
>>>>> perhaps you did not update the data set short names?
>>>>>
>>>>> Lars
>>>>>
>>>>> On Tue, Sep 1, 2015 at 11:50 AM, Calle Hedberg <
>>>>> calle.hedberg@xxxxxxxxx> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> I've got a baffling problem (presumably related to some kind of
>>>>>> caching):
>>>>>>
>>>>>> 1. yesterday I updated various data records using pgremote, including
>>>>>> data set names. We restarted tomcat after the updates.
>>>>>>
>>>>>> 2. I've also cleared my browser cache, the DHIS2 cache, updated
>>>>>> resource tables, etc.
>>>>>>
>>>>>> 3. When I now open the list of data sets, all the changed/new names
>>>>>> are showing as expected.
>>>>>>
>>>>>> 4. BUT when I run Data Integrity, a few violations related to data
>>>>>> sets are coming up AND THE DATA SET NAMES ARE THE OLD ONES.
>>>>>>
>>>>>> Any ideas what could cause this weird behaviour?
>>>>>>
>>>>>> Regards
>>>>>> Calle
>>>>>>
>>>>>> *******************************************
>>>>>>
>>>>>> Calle Hedberg
>>>>>>
>>>>>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>>>>>
>>>>>> Tel/fax (home): +27-21-685-6472
>>>>>>
>>>>>> Cell: +27-82-853-5352
>>>>>>
>>>>>> Iridium SatPhone: +8816-315-19274
>>>>>>
>>>>>> Email: calle.hedberg@xxxxxxxxx
>>>>>>
>>>>>> Skype: calle_hedberg
>>>>>>
>>>>>> *******************************************
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lars Helge Øverland
>>>>> Lead developer, DHIS 2
>>>>> University of Oslo
>>>>> Skype: larshelgeoverland
>>>>> http://www.dhis2.org <https://www.dhis2.org>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *******************************************
>>>>
>>>> Calle Hedberg
>>>>
>>>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>>>
>>>> Tel/fax (home): +27-21-685-6472
>>>>
>>>> Cell: +27-82-853-5352
>>>>
>>>> Iridium SatPhone: +8816-315-19274
>>>>
>>>> Email: calle.hedberg@xxxxxxxxx
>>>>
>>>> Skype: calle_hedberg
>>>>
>>>> *******************************************
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Jason P. Pickering
>>> email: jason.p.pickering@xxxxxxxxx
>>> tel:+46764147049
>>>
>>
>>
>>
>> --
>>
>> *******************************************
>>
>> Calle Hedberg
>>
>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>
>> Tel/fax (home): +27-21-685-6472
>>
>> Cell: +27-82-853-5352
>>
>> Iridium SatPhone: +8816-315-19274
>>
>> Email: calle.hedberg@xxxxxxxxx
>>
>> Skype: calle_hedberg
>>
>> *******************************************
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19274

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************

Follow ups

References