[HACKERS] JSON Patch (RFC 6902) support?

such as: // applies a JSON Patch json_patch_apply(json, patch) // diffs two JSON objects and produces a JSON Patch json_patch_diff(json a, json b) Thanks, Ryan Pedela

Re: [HACKERS] PL/pgSQL 2

If PL/Javascript is a serious consideration, how will int64 and numeric be handled? Thanks, Ryan Pedela Datalanche CEO, co-founder www.datalanche.com rped...@datalanche.com 513-571-6837 On Tue, Sep 2, 2014 at 6:38 AM, Andrew Dunstan and...@dunslane.net wrote: On 09/02/2014 05:44 AM, Álvaro

Re: [HACKERS] deparsing utility commands

On Wed, Mar 25, 2015 at 11:59 AM, Alvaro Herrera alvhe...@2ndquadrant.com wrote: * Should we prohibit DDL from within event triggers? Please don't prohibit DDL unless there is a really, really good reason to do so. I have several use cases in mind for event triggers, but they are only useful

Re: [HACKERS] deparsing utility commands

excited about, and I am happy to see progress. Thanks, Ryan Pedela

Re: [HACKERS] jsonb concatenate operator's semantics seem questionable

path in the JSON object. It looks like that is possible with the minus operator and jsonb_replace(). This is great, however it took me awhile to figure out the path syntax. I think adding a paragraph to the docs explaining the path syntax would help. Ryan Pedela

Re: [HACKERS] jsonb concatenate operator's semantics seem questionable

On Mon, May 18, 2015 at 8:41 AM, Ryan Pedela rped...@datalanche.com wrote: On Sun, May 17, 2015 at 9:41 PM, Josh Berkus j...@agliodbs.com wrote: Is there a particular reason why + makes more sense as shallow concatination and || makes more sense as deep concatination? Like, something in JS

Re: [HACKERS] jsonb concatenate operator's semantics seem questionable

On Mon, May 18, 2015 at 12:24 PM, Josh Berkus j...@agliodbs.com wrote: On 05/18/2015 08:57 AM, Ryan Pedela wrote: If not, deep concatenation would solve this problem, but I can also see another solution. Use + for shallow concatenation since it really means add element to top-level path

Re: [HACKERS] jsonb concatenate operator's semantics seem questionable

On Wed, May 20, 2015 at 12:34 PM, Andrew Dunstan and...@dunslane.net wrote: So Dmitry, at my suggestion, has come up with a way of doing that, by adding a parameter to jsonb_replace(). If this parameter is set to true (it defaults to false) and the key or array element pointed to by the last

Re: [HACKERS] [PATCH] Generalized JSON output functions

On Fri, May 22, 2015 at 10:51 AM, Merlin Moncure mmonc...@gmail.com wrote: On Fri, May 22, 2015 at 9:43 AM, Alvaro Herrera alvhe...@2ndquadrant.com wrote: Andrew Dunstan wrote: On 05/20/2015 09:16 AM, Shulgin, Oleksandr wrote: Attached is a patch against master to generalize the

Re: [HACKERS] [PATCH] Generalized JSON output functions

stupid things with large numbers. In addition, ES7 is introducing value types which will hopefully solve the large number problem in Javascript. The random whitespace issue is valid in my opinion and should be fixed. Thanks, Ryan Pedela

Re: [HACKERS] [PATCH] Generalized JSON output functions

On Wed, Jul 15, 2015 at 11:10 AM, Ryan Pedela rped...@datalanche.com wrote: On Wed, Jul 15, 2015 at 8:52 AM, Robert Haas robertmh...@gmail.com wrote: FWIW, I don't agree. If it's not easy to read the JSON that PostgreSQL generates using JavaScript, then a lot of people are just going

Re: [HACKERS] [PATCH] Generalized JSON output functions

On Wed, Jul 15, 2015 at 8:52 AM, Robert Haas robertmh...@gmail.com wrote: FWIW, I don't agree. If it's not easy to read the JSON that PostgreSQL generates using JavaScript, then a lot of people are just going to give up on doing it, and IMO that would be sad. Telling people that they have

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Mon, Sep 28, 2015 at 4:09 PM, Jim Nasby wrote: > On 9/28/15 11:43 AM, Andres Freund wrote: > >> On 2015-09-28 09:41:18 -0700, David Fetter wrote: >> >>> Since you're convinced that this is an unqualified win, please put >>> together a project plan for switching from

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

an issue is created or updated. 2. Replies to the email will automatically update the issue on Github. 3. Github is where most of the OSS activity happens now. 4. If Github goes away, so what? The core workflow never changes. Thanks, Ryan Pedela

Re: [HACKERS] Add jsonb_compact(...) for whitespace-free jsonb to text

On Tue, Apr 26, 2016 at 10:49 AM, Stephen Frost <sfr...@snowman.net> wrote: > * Ryan Pedela (rped...@datalanche.com) wrote: > > On Sun, Apr 24, 2016 at 4:02 PM, Sehrope Sarkuni <sehr...@jackdb.com> > wrote: > > > The default text representation of jsonb adds whit

Re: [HACKERS] Add jsonb_compact(...) for whitespace-free jsonb to text

On Sun, Apr 24, 2016 at 4:02 PM, Sehrope Sarkuni wrote: > Hi, > > The default text representation of jsonb adds whitespace in between > key/value pairs (after the colon ":") and after successive properties > (after the comma ","): > > postgres=# SELECT

Re: [HACKERS] Calling json_* functions with JSONB data

On Mon, May 23, 2016 at 11:14 AM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Mon, May 23, 2016 at 12:55 PM, Peter van Hardenberg wrote: > >> Hi there, >> >> I noticed it was very easy to accidentally call the json_* form of JSON >> manipulation functions with jsonb

Re: [HACKERS] Html parsing and inline elements

Apache Tika [1] for plain text extraction from HTML. There are so many weird edge cases when parsing HTML that it is easier to use something that is already mature than reinventing the wheel. 1. https://tika.apache.org/ Thanks, Ryan Pedela

Re: [HACKERS] 9.6 phrase search distance specification

On Thu, Aug 11, 2016 at 9:27 AM, Oleg Bartunov <obartu...@gmail.com> wrote: > On Tue, Aug 9, 2016 at 9:59 PM, Ryan Pedela <rped...@datalanche.com> > wrote: > > > > > > > I would say that it is worth it to have a "phrase slop" operator

Re: [HACKERS] 9.6 phrase search distance specification

On Thu, Aug 11, 2016 at 10:42 AM, Ryan Pedela <rped...@datalanche.com> wrote: > On Thu, Aug 11, 2016 at 9:27 AM, Oleg Bartunov <obartu...@gmail.com> > wrote: > >> On Tue, Aug 9, 2016 at 9:59 PM, Ryan Pedela <rped...@datalanche.com> >> wrote: >>

Re: [HACKERS] 9.6 phrase search distance specification

On Tue, Aug 9, 2016 at 12:59 PM, Ryan Pedela <rped...@datalanche.com> wrote: > > > Thanks, > > Ryan Pedela > Datalanche CEO, founder > www.datalanche.com > > On Tue, Aug 9, 2016 at 11:58 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > >> Bruce Momjian

Re: [HACKERS] 9.6 phrase search distance specification

Thanks, Ryan Pedela Datalanche CEO, founder www.datalanche.com On Tue, Aug 9, 2016 at 11:58 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Bruce Momjian <br...@momjian.us> writes: > > Does anyone know why the phrase distance "<3>" was changed from "at mos