Subject | Re: [Firebird-Architect] Re: [firebird-support] BLOB Filter |
---|---|
Author | Jim Starkey |
Post date | 2004-06-01T15:07:25Z |
Dimitry Sibiryakov wrote:
specifying a blob type at runtime was so blobs in single table could
have different blob types. One of the models I used in designing the
feature was marked up text -- straight Ascii, runnoff, troff, tex --
intermixed in a document table with filters to fetch whatever target
format was required.
The engine's responsibility is to store and fetch blobs, and if asked
politely, find a filter to go from A to B. It was never intended that
the feature would restrict usage.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
>It was never intended to be enforced. In fact, the whole reason for
>
> IMHO, it is a design flaw. Server must enforce type of stored data.
>I don't want to guess what Jim was thinking about, designing BLOB
>filtering (if it was him).
>
specifying a blob type at runtime was so blobs in single table could
have different blob types. One of the models I used in designing the
feature was marked up text -- straight Ascii, runnoff, troff, tex --
intermixed in a document table with filters to fetch whatever target
format was required.
The engine's responsibility is to store and fetch blobs, and if asked
politely, find a filter to go from A to B. It was never intended that
the feature would restrict usage.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376