Content-Type: multipart/signed;
 boundary="Apple-Mail=_15EA683F-5288-4690-AF9F-3992C21E1392";
 protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST
 opclass documentation)
From: "David E. Wheeler" <david@justatheory.com>
In-Reply-To: <29011.1399415977@sss.pgh.pa.us>
Date: Tue, 6 May 2014 15:54:19 -0700
Cc: Peter Geoghegan <pg@heroku.com>, Bruce Momjian <bruce@momjian.us>,
 Greg Stark <stark@mit.edu>, Robert Haas <robertmhaas@gmail.com>,
 Heikki Linnakangas <hlinnakangas@vmware.com>,
 Andrew Dunstan <andrew@dunslane.net>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Message-Id: <5EE1519A-7DF7-4EB0-B7EA-5492F5F53C63@justatheory.com>
References: 
 <CAM3SWZQzOxmryVe_bdu9WhqbJTBoiqM7knvKm0oRYxvfsFnz7Q@mail.gmail.com>
 <534475B7.6020908@dunslane.net> <5344EAA4.1050605@vmware.com>
 <CA+TgmoZucoe-w5P_16A-gdfRBFCCu7PD17YO-KqrYPBhb5TxAA@mail.gmail.com>
 <30137.1397057056@sss.pgh.pa.us>
 <CAM-w4HNawF2sPDSUrZsng7zgGnste-Vy1+42AufyVq9UkVeCZw@mail.gmail.com>
 <20140422223230.GL10046@momjian.us> <16527.1398214220@sss.pgh.pa.us>
 <20140506201048.GI30817@momjian.us> <16769.1399407530@sss.pgh.pa.us>
 <20140506212020.GK30817@momjian.us>
 <57E8AA44-F816-45F2-BB61-5A854FFB0A97@justatheory.com>
 <28554.1399414853@sss.pgh.pa.us>
 <CAM3SWZS4Tn-xZOBqM_ds-nhB2wLSpKG86rcJnMSexqDJqWgzNg@mail.gmail.com>
 <29011.1399415977@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--Apple-Mail=_15EA683F-5288-4690-AF9F-3992C21E1392
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On May 6, 2014, at 3:39 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Meh.  I would not think that that represents effective use of JSON:
> if the rows are all the same, why aren't you exposing that structure
> as regular SQL columns?  IMHO, the value of JSON fields within a SQL
> table is to deal with data that is not so well structured.

The use of JSON will not be ideal -- not in this sense. For example, at =
$work, we=92re using it in place of an EAV model. Hence most rows have =
the same keys (or a subset of known keys). Or think of your favorite =
JSON API: every call to http://api.pgxn.org/user/$username.json is going =
to have a very similar structure.

> In any case, it was certainly the complaint that insertions might
> fail altogether that made me (and I assume others) want to not have
> jsonb_ops as the default opclass.  Is there a good reason not to
> fix that limitation while we still can?

Fixing++

David


--Apple-Mail=_15EA683F-5288-4690-AF9F-3992C21E1392
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTaWgbAAoJEJLfYnT4yIHxfpEP/39UJeMdtrG+/5L8mmpKaviP
QMYVnjDKkqUjU/8AEgvEakd84wMUJ9J55J02ece+h/ZkDVd1vgZK0BeoGjFxMHQk
k2M+WEiIjDJuqrI4lk0xIVKUm/LFyPVLlIn8NtBIatP2a5kiXLbx/yTXjT4BHl3r
YQTYsMcCcEsaKaorEBocCHNN23Ft23D6MvsPTKKrI2yxxZUaUsR3BbBrYH35M6nZ
lrsOQrreoqRma0uzBoTMiG3fO+y5WokIzGimgDD3p7UUX5qiSoCeEgWPyLZPf3JA
F33y8kkS3cbz2/h0e79Uk0/dvBUsZrSJ0ItEIx3FtCW9fHXqd9O+zmMeTFYkAaqB
qdGdjI6xDj0VsPQbXUHPfpmBipkxvPlzajoJgNKgrwfOVSOVdtZ78W07WrmUsQ0/
PvYy8Ov1VUwaIwg7WVpvESfMKh4un/3TeR6/lUSzlYBa/zKVUoHvLb7hKqtMg9sc
+5SUEoKLyU3FHEoFgvSHt0GEd4Ga11uawgmVYU0Vy6bXGf2vt+niOepmeaVoOGJY
1uK0/u4d6tOevxLTdfR5SiP5JoxS2aXfUfwTif94mkDnsSnn1gH66tyl1Wgjh9Dv
obS+313FcY8niCePFNsH6sncOwOJv3Qj5QVGS2Rp5/mKaJzIfa8P/+aP2qsELJxb
GnG+Q9ZyakSKx63IilzM
=XrLA
-----END PGP SIGNATURE-----

--Apple-Mail=_15EA683F-5288-4690-AF9F-3992C21E1392--