Store discovery data result to prevent mapping each request about lodata HOT 6 CLOSED

Hi, a null value should store forever (same as rememberForever). My aim for lodata is to make it as developer friendly out of the box as possible, which is why the default value is 0 to prevent caching while you're playing around with discovery!

from lodata.

Wow, I did predict this functionality would eventually be needed but 8s is extreme! I'll work out a developer-friendly way of managing this.

from lodata.

Alright Thanks! Most of the time goes to each INFORMATION_SCHEMA.KEY_COLUMN_USAGE query fetching the keys from each and every table every request, which takes about ~0.5s per query on our production server. I expect that smaller servers tend to have quite a bit faster responsetime.

If you need any details, feel free to let me know!

from lodata.

Hi, this functionality introduced in https://github.com/flat3/lodata/releases/tag/v5.0.1 - let me know if the new config options work for your use case

from lodata.

It does seem to work yes, only i noticed that having the ttl at 0 does mean it won't be stored at all. I guess it should be ->rememberForever(...) when ttl is 0. But after setting it to something above 0 it does seem to work.

Thanks that you use the Laravel Cache functionality, I also have the ability to create my own functionality that has the ability to check for database changes in the background, and if so deletes the cache key and re-do the discovery without it having to influence the end-user.

Thanks!

from lodata.

Oops, I've seemed to misread it, my bad! null does work indeed, thank you!

from lodata.