Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

wwwxxx0cm, www.webdp.net, Event 9 IIS log failed to write entry, wwwxxx jeffs, Catastrophic failure Unexpected method call sequence. 0x8000ffff (-2147418113)., ksh lock a file, [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed, sed: -e expression #1, char 1: unterminated address regex, procmail + change subject, w2ksp4.exe download

Links

XODOX
Impressum

#1: Using bytea as an argument.

Posted on 2011-01-12 14:06:03 by Christopher Hotchkiss

--0016364189610397df0499a5dd7e
Content-Type: text/plain; charset=ISO-8859-1

To All,
I am attempting to call a function in Postgres 9 on Windows using the ODBC
driver and am finding that the parameter with embedded nulls is getting
truncated when I check the server log. Is calling a function that takes a
bytea supported? I know its not explicitly listed in the list of supported
types. Should I just hex encode the values instead?

Thanks!
--
Christopher Hotchkiss "chotchki"
http://www.chotchki.us

--0016364189610397df0499a5dd7e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

To All,<br>I am attempting to call a function in Postgres 9 on Windows usin=
g the ODBC driver and am finding that the parameter with embedded nulls is =
getting truncated when I check the server log. Is calling a function that t=
akes a bytea supported? I know its not explicitly listed in the list of sup=
ported types. Should I just hex encode the values instead?<br clear=3D"all"=
>
<br>Thanks!<br>-- <br>Christopher Hotchkiss &quot;chotchki&quot;<br><a href=
=3D"http://www.chotchki.us">http://www.chotchki.us</a><br>

--0016364189610397df0499a5dd7e--

Report this message