Moritz Poldrack

I would prefer the 8-10 option, as this would also fix the storage scope issue on GrapheneOS

On Sun 02 Jun 2024 05:11:53, ccoVeille wrote: > +func (e *Engine) modifyEnvironment(c *exec.Cmd) { > > By bare return, I meant using `return c`everywhere and not `return` That is...

OS handling of environment variables and Go stdlib. -- Moritz Poldrack https://moritz.sh > No alcohol, dogs or horses.

> why do u just pass env var like this: > > `A=B air` mainly two reasons: - No way to change the environment between restart, which at times can...

That was an approach I was considering, but ultimately abandoned it because .env files or some variation of them are usually already present. And having two places to maintain environment...

Since this is in a sense an extension to MySQL, this should probably be accompanied by a warning about this type not being available in all server implementations.

Okay, I've taken a look, and it seems to be something for `github.com/pingcap/tidb`'s parser, which would probably involve a lot of convincing. Any idea on how to do it better?