Well Frank you say 16MB so I think that rules out VARCHAR. I've
JSON functions and they seem to work really well. So, I think it's
simple question. Will all your documents be properly formatted
documents, and will you need to perform JSON functionality within
database access layer in taking advantage of the DB2 functions to
application development? If the answer is yes, then store them in
If the only reason for the database is to store and retrieve then
CLOB. You can always apply the functions to the CLOB data if you
use SQL to extract data from JSON documents.
On 09.06.2017 12:34, Frank Fella wrote:
> We are thinking about storing JSON documents in columns of a
DB2 table. Research has shown me that I have the option of storing
it in a VARCHAR, CLOB to keep it in text format or BLOB to store it
in BSON format using the scalar functions BSON2JSON and JSON2BSON
when retrieving and storing the JSON document.
> Each JSON document will be well under the 16M limit I
understand is imposed on JSON/BSON objects.
> Does anyone have advice/guidelines where one might choose one
option over the other? Any performance issues I should be aware
> Frank J. Fella, Developer, Progressive Insurance
> [login to unmask email]
> -----End Original Message-----