I heard it was fixed too but looking around, I found nothing. I added
it tonight to the types section.
> Thomas,
>
> You are correct about the poor documentation for bytea. I hear this is
> fixed in 7.2 docs, but haven't verified. I learned about it myself by
> looking at the internal pg_*
I have added a description to the CVS and it will appear in 7.2. It is
in the development docs now.
> Hi Barry,
>
> I looked in the postgresql documentation and couldn't find any mention
> of a "bytea" type. Well actually, I found ..
>
> $ grep -i bytea *
> bki-commands.html:>bytea catalog-pg
Thomas,
You are correct about the poor documentation for bytea. I hear this is
fixed in 7.2 docs, but haven't verified. I learned about it myself by
looking at the internal pg_* tables and seeing how they used it.
I'm glad to hear that you have a workaround for your original issue.
thanks,
Hi Barry,
I looked in the postgresql documentation and couldn't find any mention
of a "bytea" type. Well actually, I found ..
$ grep -i bytea *
bki-commands.html:>byteabyteabytea(bytea *) Thomas,
>
> The text datatypes in postgres (i.e. char, varchar, text) do not support
> storing null charac
Thomas,
The text datatypes in postgres (i.e. char, varchar, text) do not support
storing null characters. If your data contains nulls then you need to
use the binary datatype bytea. Unfortunately the JDBC drivers do not
currently support the bytea datatype.
thanks,
--Barry
Thomas O'Dowd wr
I found problem. My string has a null character in the middle of it. I
noticed from the Connection.java code that the null character idicates
end of query so I guess that is what is happening. I'll strip out my
null strings in the mean time as they are not needed before sending them
to the driver
Thanks Barry,
I turned on debugging in postgresql. I found that the query is being truncated
and is not fully making it to the backend, therefore I'm getting the
Unterminated string error. I'll have a look into why and report back if
I find anything.
Cheers,
Tom.
On Tue, Aug 28, 2001 at 12:56
Thomas,
If you turn on debug messages on the server to print out the SQL
statements it receives you should be able to get the exact string that
the server is receiving from the client and failing on. That might help
you find the problem.
thanks,
--Barry
Thomas O'Dowd wrote:
> Hi all,
>
> I
