| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-01-28 16:33:05 |
| Message-ID: | 52E7DBC1.10007@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/28/2014 11:27 AM, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> Tom Lane wrote:
>>> Practically every existing use of <indexterm> is freer than this in its
>>> use of whitespace. It sounds to me like maybe you are trying to put the
>>> <indexterm> inside something it shouldn't go inside of.
>> FWIW I was just talking about formatting of the SGML source so that it
>> is easier to read.
> Yeah, me too. I'm just suggesting that maybe Andrew needs to move the
> indexterm so that he can format it more readably.
>
>
Hmm. Maybe I could put them inside the para elements. So we'd have:
<entry><para>
<indexterm>
</indexterm>
para text
</para><para>
<indexterm>
</indexterm>
para text
</para></entry>
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-01-28 16:36:39 | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Previous Message | Bruce Momjian | 2014-01-28 16:29:52 | Re: Function definition removed but prototype still there |