Re: Elevator speech on DB2 development and web enablement?

[Bradley Stone <bvstone@xxxxxxxxx>]

There's a difference between storing it as the original data (as a record
of what you received) and storing it to use for all interaction with the
data.   That's what the reference was.

But I strongly agree stream files vs BLOB/CLOB for storage is the way to go.

Brad
www.bvstools.com

On Fri, Oct 2, 2015 at 1:48 AM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

> 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