kind of a bag of attributes in a DB . . .

From: Albretch Mueller <lbrtchx(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: kind of a bag of attributes in a DB . . .
Date: 2019-09-07 12:45:19
Message-ID: CAFakBwhouhfEPCG3Mbo--zNveCPQ2s4rvyVb378FkJvZ=PhgrQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Say, you get lots of data and their corresponding metadata, which in
some cases may be undefined or undeclared (left as an empty string).
Think of youtube json files or the result of the "file" command.

I need to be able to "instantly" search that metadata and I think DBs
are best for such jobs and get some metrics out of it.

I know this is not exactly a kosher way to deal with data which can't
be represented in a nice tabular form, but I don't find the idea that
half way off either.

What is the pattern, anti-pattern or whatever relating to such design?

Do you know of such implementations with such data?

lbrtchx

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-09-07 18:02:07 Re: Environment Variable for --data-checksum during initdb
Previous Message Ray Cote 2019-09-07 12:32:39 Re: Environment Variable for --data-checksum during initdb