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

From Adrian Klaver
Subject Re: kind of a bag of attributes in a DB . . .
Date
Msg-id 9c4ec0b8-11a1-a696-08dc-51f2c4a78019@aklaver.com
Whole thread Raw
In response to kind of a bag of attributes in a DB . . .  (Albretch Mueller <lbrtchx@gmail.com>)
Responses Re: kind of a bag of attributes in a DB . . .
List pgsql-general
On 9/7/19 5:45 AM, Albretch Mueller wrote:
> 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.

Is the metadata uniform or are you dealing with a variety of different data?


> 
> 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
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Environment Variable for --data-checksum during initdb
Next
From: Adrian Klaver
Date:
Subject: Re: Convert a row to a nested JSON document containing all relationsin PostgreSQL