kind of a bag of attributes in a DB . . .
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
Re: kind of a bag of attributes in a DB . . .
On 9/7/19, Adrian Klaver wrote: > Is the metadata uniform or are you dealing with a variety of different > data? You can expect for all files to have a filename and size, but their kinds (the metadata describing them) can be really colorful and wild when it comes to formatting. lbrtchx
Re: kind of a bag of attributes in a DB . . .
On 9/10/19, Adrian Klaver wrote: > If there is no rhyme or reason to the metadata I am not sure how you > could come up with an efficient search strategy. Seems it would be a > brute search over everything. Not exactly. Say some things have colours but now weight. You could still Group them as being "weighty" and then tell about how heavy they are, with the colorful ones you could specify the colours and then see if there is some correlation between weights and colours ... lbrtchx
Re: kind of a bag of attributes in a DB . . .
just download a bunch of json info files from youtube data Feeds Actually, does postgresql has a json Driver of import feature? the metadata contained in json files would require more than one small databases, but such an import feature should be trivial C
