restoring clearCachedConfig()

[ArtificialOwl]

restoring clearCachedConfig() that was removed in 25.0.0 with #32261

It can be useful in some use-case when config is edited by a parallel process

[ArtificialOwl]

/backport to stable25

[juliusknorr]

What exactly would be the use case there? If it is used in any app it probably should become a method on the public interface.

[ArtificialOwl]

What exactly would be the use case there? If it is used in any app it probably should become a method on the public interface.

IAppConfig is not really kept up to date with AppConfig, but I totally agree that we should spent some time on this.

Now the use cases: oc_appconfig is perfect for any app that wants to store some values without creating it's own small table for the same result.
A cronjob or an interactive occ command might:

• needs to cycle an heavy process,
• wants to confirm a general settings/status from time to time.

(ie. this is used to avoid duplicate index by fulltextsearch)

If the app can refresh the cache of oc_appconfig before checking the status from time to time it will not need to create it's own table for the same result.

[juliusknorr]

(ie. this is used to avoid duplicate index by fulltextsearch)

Sounds more like a case for https://github.com/nextcloud/server/blob/fcae6a68c347e2913cc29f45648be37789f09c29/lib/public/Lock/ILockingProvider.php

Now the use cases: oc_appconfig is perfect for any app that wants to store some values without creating it's own small table for the same result.
A cronjob or an interactive occ command might:
needs to cycle an heavy process,
wants to confirm a general settings/status from time to time.

While I know that is common behavior and used to also heavily make use of that, we might want to avoid this in the future due to the fact that all entries of oc_appconfig are loaded on every request. Maybe we could rather come up with a way to have a spearate config table for such things where entries are only queried from the DB when necessary - or introduce two types of values in oc_appconfig. Ones that are always loaded and others that apps need to request individually.

Would be good to see what @PVince81 thinks about that.

[juliusknorr]

I'm not fully against getting this one back in, just that I think it might make sense to be careful how oc_appconfig is being (ab)used ;)

[PVince81]

👍 as discussed before with @ArtificialOwl

[juliusknorr]

Failure unrelated