| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch>, Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com> |
| Cc: | postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Internationalisation (i18n) with Postgres as backend |
| Date: | 2021-06-02 08:38:26 |
| Message-ID: | 96915d0c324145f661eca9298d4de90d2df43cd7.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2021-06-01 at 23:08 +0000, Laura Smith wrote:
> I didn't consider hstore, I did consider jsonb though.
>
> The thing that made me lean towards individual rows rather than consolidated was
> that I thought versioning would ultimately be easier/cleaner to achieve with
> individual rows (e.g. using tsrange & gist exclude). But willing to be proven wrong.
Your intuition is good. Don't use JSON for that, and don't use the outdated
hstore extension in particular.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2021-06-02 08:43:42 | Re: Internationalisation (i18n) with Postgres as backend |
| Previous Message | Laura Smith | 2021-06-02 07:08:04 | Re: Internationalisation (i18n) with Postgres as backend |