Re: bytea problem
От | chris humphrey |
---|---|
Тема | Re: bytea problem |
Дата | |
Msg-id | 4ECC043E.9070807@parallelsw.com обсуждение исходный текст |
Ответ на | Re: bytea problem (Maciek Sakrejda <msakrejda@truviso.com>) |
Список | pgsql-jdbc |
I looked at the types of ways to store the data, and ensuring it was hex, I could see the '\x' at the beginning of the string... Once I matched the driver with the db all was happy. May want to update the jdbc driver to know what version of db it is talking to and either make the code compatable between the versions, or reject the connection if it is the wrong (incompatable) version.... Once things started working for me, I got lazy and stopped thinking about the problem.... On 11/22/2011 1:15 PM, Maciek Sakrejda wrote: >> I read a posting that the bytea datatype was refactored in version 9, and >> one indication was that twice as many bytes came out as went in... > I think the change in this default is what Chris is referring to: > > http://www.postgresql.org/docs/9.0/static/runtime-config-client.html#GUC-BYTEA-OUTPUT > > This certainly could affect what you're doing. > --- > Maciek Sakrejda | System Architect | Truviso > > 1065 E. Hillsdale Blvd., Suite 215 > Foster City, CA 94404 > (650) 242-3500 Main > www.truviso.com >
В списке pgsql-jdbc по дате отправления: