[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue
From: |
Yair Lenga |
Subject: |
Re: Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2) |
Date: |
Wed, 7 Sep 2022 06:58:14 -0400 |
Another comment:
While it’s important to use “natural” access, I believe it is ok to have a
command to set values inside the h-value. It does not have to be supported as
part of …=… , which has lot of history, rule, interaction with env var, etc. I
think something like:
hset var.foo.bar=value
hset var.{complex.$x}=value
Are ok. Does not have to be hset - just borrowed it from redis. :-). Having a
separate command can simplify implementation - less risk to break existing code.
Yair
Sent from my iPad
> On Sep 7, 2022, at 3:19 AM, Martin D Kealey <martin@kurahaupo.gen.nz> wrote:
>
> So may I suggest a compromise syntax: take the ${var.field} notation from
> Javascript, and the {var.$key} as above, but also extend it to allow
> ${var.{WORD}} (which mimics the pattern of allowing both $var and ${var})
> with the WORD treated as if double-quoted. Then we can write
> ${var.{complex.$key/$expansion}} and var.{complex.$key/$expansion}=value,
> which are much more reasonable propositions for parsing and reading
- Re: bug-bash Digest, Vol 238, Issue 2, Yair Lenga, 2022/09/04
- Re: bug-bash Digest, Vol 238, Issue 2, Martin D Kealey, 2022/09/05
- Re: bug-bash Digest, Vol 238, Issue 2, Yair Lenga, 2022/09/05
- Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2), Martin D Kealey, 2022/09/07
- Re: Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2), Yair Lenga, 2022/09/07
- Re: Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2), Martin D Kealey, 2022/09/12
- Re: Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2),
Yair Lenga <=