Re: [Ur] Key-value store extension

It seems like it should be simple to implement a Functor that has the same semantics (if not number-of-tables efficiency) as the proposed keyword. This approach is taken in, for instance, UPO's linear state machine . On Wed, Jan

Re: [Ur] Key-value store extension

I have, but in my opinion it's convenient to be able to change some less important things from within the application. For example, I have a sort of readme in the front page of my application which I don't want to put in its own table because it's the only one in the whole application, but I also

Re: [Ur] Key-value store extension

That's an interesting idea.  It is not a feature that has ever occurred to me to suggest.  I prefer to settle configuration at compile time, so that the compiler can specialize code to chosen settings.  Have you considered that path, too? On 01/29/2018 10:43 AM, Athene Noctua wrote: Hi all,

[Ur] Key-value store extension

Hi all, I find it useful to have a module for storing global configuration settings and the likes in my applications, using a single table with key and value fields and a simple get/set interface. Unfortunately this approach breaks the nice encapsulation properties you get with Ur/Web tables, as