Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Madison Pruet — — source: Usenet: comp.databases.informix
Ben Thompson wrote:
> Madison Pruet wrote:
>
>> I need an idea of the number of customers who are using blobspace
>> blobs as opposed to smart blobs. That is - how many customers are
>> using BYTE/TEXT as opposed to BLOB/CLOB
>>
>> Also I need some idea of the impact of not having HDR support
>> blobspace blobs.
>
> We would regard the loss of this functionality as bad news. It would
> force us to rewrite a lot of code to do separate writes to two different
> instances and cease upgrading in the mean time.
>
> Ben.
Ben - I am talking about BYTE/TEXT which are stored in a blobspace. I
am not talking about BYTE/TEXT which are stored in the tablespace.
If you enable logging on the BLOB/CLOB smart blobs or used tablespace
BYTE/TEXT within a logging database, then the large objects can be
replicated via HDR. Blobspace BYTE/TEXT columns have never been able to
be replicated via HDR because they are not logged.
I am not talking about removing functionality.
M.P.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.