pkoppstein

@fadado - Thank you so much for your inspiration. Over at https://gist.github.com/pkoppstein/bbbbdf7489c8c515680beb1c75fa59f2 I've posted a parser that is similar to @fadado's but with an emphasis on efficiency (see "Performance" below),...

Unfortunately I don't understand the connection you have in mind between `eval(_)` and I/O handle types, but I'd happily settle for a filter that takes a string as its argument,...

@georgir - Thanks for your interest and insights. I agree that we should put the desired semantics in the driver's seat, at least at this stage. For the "use case"...

@nicowilliams wrote: > We need both. So how about: ``` eval( STRING, null ) ~~ vanilla context eval( STRING, true) ~~ caller's context eval( STRING, CONTEXT) ~~ context specified by...

To summarize, as I understand it, the general form of `eval` will be ``` eval(STRING; CONTEXT) ``` where STRING is a string that will be compiled in a context specified...

@seansund wrote: > The json is an array of items, each one having an id. I'd like to use jsonpath to find the item with id=X For those who don't...

Also reproduced in v1.0.1-dev5305 Since DuckDB ought to be able to read valid JSON, this Issue ought to be regarded as a bug report.

> Your reproduction fails with > > ``` > Catalog Error: Scalar Function with name list_update does not exist! > ``` Whoops. Sorry. Over-zealous attempt at pruning. Fixed.

Very impressive! I followed your directions for viewing the documentation and would just point out that they assume 'markdown' is already installed. Here is a batch of comments and suggestions...

@01mf02 wrote: > I've integrated all of them I hope that means you found them useful :-) > markdown I just installed it. Here's Batch #2: 8) Re: > It...