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.
John H. Frantz — — source: Informix-list mailing list archive (1991-1998)
Carlos Palma <cap@smd.pt> wrote:
>
> I've posted before one article similar to this, but as no answer came
> by (except one sugestion concerning escapes, which didn't work) I'm
> reposting it with another 'look':
>
> Anyone know what datatype should have a column that is intended to
> store non-printable characters ?
>
> CHAR column's do not do it !
> I want to store characters like ^M (control-M or carriage return) and
> ^J (control-J or linefeed) in a memo-type field like 'observations'.
> I want to use this in ESQL.
>
> Any help will be appreciated !
Perhaps you should just store the control characters in a CHAR column
as you wrote them in your article (e.g. "^M") and use a function or
a stored procedure to 'decode' them when you use them. That way you
can browse the data normally (like with dbaccess) without having to
worry about strange things happening on your screen.
Just a thought.
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.