kind of a bag of attributes in a DB . . . - Mailing list pgsql-general

From Albretch Mueller
Subject kind of a bag of attributes in a DB . . .
Date
Msg-id CAFakBwhouhfEPCG3Mbo--zNveCPQ2s4rvyVb378FkJvZ=PhgrQ@mail.gmail.com
Whole thread Raw
Responses Re: kind of a bag of attributes in a DB . . .  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: kind of a bag of attributes in a DB . . .  (Chris Travers <chris.travers@gmail.com>)
List 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



pgsql-general by date:

Previous
From: Ray Cote
Date:
Subject: Re: Environment Variable for --data-checksum during initdb
Next
From: Adrian Klaver
Date:
Subject: Re: Environment Variable for --data-checksum during initdb