[merk]

Originally Posted by KirbyDE

Ah, now there we go.
Sure, that would be possible - with the dabwack of having an additional Query for every Pageload.
And that's what the discusssion here is all about: Which approach adds the smallest Overhead possible?


The Datastore Classes will take care of Updates, that's not a Problem.

<!-- edit: this bit can be ignored, next para solves the solution in my opinion: As far as i can see there will only ever need to be ONE query if the item doesnt exist in the other datastore types' storage. Not fully grasping what happens with them, i suspect thats how it works. (At least thats how it appears to look).

After the single query on the first pageload it is requested on has passed, there will be no more queries. -->

There also wont be any queries if the product builds its datastore item using the class, because the class will deal with the build and will put it into the proper storage.

And as long as the product manages datastore changes properly - it isnt an issue.