Re: Elevator speech on DB2 development and web enablement?

Weel If you use XML or JSON to send business documents like an
invoice many countries laws require you to store the recieved data
in the original format.

However using BLOB or CLOB in DB2 is a bad idear:

a. how do you display or edit a XML of JSON document in a BLOB/CLOB
field? There are no simple editors!

b. How do you copy a BLOB/CLOB field from one row to another?

c. how do you handle different Unicode codepages like UTF-8 or UTF-16
in RPG/COBOL?

d. Over time the DB table with BLOB/CLOB storage extension will grow
in size.

It is much easier to store the received data in IFS files and then store
the file name in a DB2 field.

One can structure ones IFS files in dir's e.g. per year or per
customer/supplier/
document type.

All PC tools will work directly on IFS files, none will work on BLOB/CLOB
fields.

This is not only for XML/JSON but also for binary data such as JPEG, GIF's
etc.



On Fri, Oct 2, 2015 at 5:37 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

I couldn't agree more about XML, JSON, <whatever it is next week> as far as
transport vs storage.

The only thing I can think of why you would store in JSON vs a RDB is
because it's "hip". Wow.. that made me sound older than I am.. haha.

Brad
www.bvstools.com

On Thu, Oct 1, 2015 at 9:15 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I was referring to the technology preview regarding JSON:

https://www.ibm.com/developerworks/ibmi/library/i-json-store-technology/

That article is more about using the QSHELL command line interface, and /
or Java API for "retrieving" JSON-formatted data. But it sounds like the
storage of JSON documents in BLOB or CLOB fields hasn't changed much.

Frankly, I can't think of a good use case for "storing" JSON or XML
documents in IBM i database tables. JSON seems like a great format for

data

interchange. But once the data arrives on IBM i, it seems that it would
work much better to extract the "data" from the document and store it in
normalized formats (tables, rows, columns).

So, I too would be interested in hearing about use-cases for storing JSON
documents in the database. Just to be like MongoDB? Why?
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.