Re: blob vs. many columns
Do you need to filter on any of the values? (That is, will any SQL statement use a float column in the WHERE clause, etc?) If so, you need to expose that column.
If not (which seems more likely), then you are probably "better off" tossing all (or most) of the values into a JSON-encoded (or XML, or YAML, or...) structure.
Such would be
* Open-ended (Tomorrow you can add another FLOAT without changing the schema.)
* Easy to handle in most languages. (JSON, at least, has convenient routines for marshalling/unmarshalling).
* Smaller (Probably less space is needed.)
Further suggestion (if space is an issue): COMPRESS, in the application, the JSON and put it into a BLOB. The blob will shrink about 3:1.
JSON (etc) can easily handle missing values.
Subject
Written By
Posted
Re: blob vs. many columns
July 05, 2012 06:10AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.