Eric and Tom: thank you very much for your help, I
will try your suggestions tomorrow at work.
The sql statements are issued from a COBOL program,
which can also issue the same statements to other
databases (MySQL, MS SQLServer), so the first thing Im
going to do is trying to change the encoding setup,
which would be the most homogeneous solution that
wouldn't interfere with the other databases, that
currently handle well those strings with hexadecimal
data.

Thank u very much again!
Luciano.


--- Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Luciano <ldelio@yahoo.com> writes:
> > I am having a problem doing a query with
> hexadecimal
> > characters through ODBC. The hexadecimal
> characters
> > are inside a character filed. It would be
> something
> > like:
>
> > SELECT * FROM MYTABLE WHERE COLUMN1 < 'XXXXXX'
>
> > but instead of the X's there are x'FF'
> characters...
> > The query is accepted, but the result is not
> > consistent... it returns an empty result set. Does
> > anyone know if I'm missing something?
>
> I suspect you are spitting byte sequences at the
> backend that are
> illegal in the character set encoding you've
> selected. Check your
> locale and database encoding setup. C/SQL_ASCII is
> the best bet
> if you want to pretend that you can store any random
> byte sequence
> in a character field.
>
> Plan B, which would probably be better in the long
> run, is to store
> that data in a bytea field instead, and send escaped
> characters
> (ie \\377 rather than an actual FF byte).
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 8: explain analyze is your friend
>




__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html