I've read this twice and I have great difficulty understanding
what the real problem is. Your posting touches on so many
subjects: character encoding, statement length, driver versions,
large objects, calling functions, large parameter values,
Could you please summarize what the problem is when you use the
latest and greatest driver (e.g. jdbc7.1-1.3.jar from
http://jdbc.fastcrypt.com) and when you use JDBC in the way its
On Tue, 28 Aug 2001 17:46:05 -0300, you wrote:
>I've been experimenting with some versions of PostgreSQL JDBC trying to find
>a version that suits the our application:
>1) It has to support portuguese characters (like áéíóú etc) directly in SQL
>2) It is desiderable that it supports SQL statements longer than 8k.
>Unfortunately the only version I found that seems to address both problems
>above (version 7.1-1.2 from jdbc.postgresql.org) seems to be broken in
>relation to data types (not gone deeper into that, yet).
>Anyway what I would like to ask is if there is a way to use "Large Object"
>code to overcome statement length restrictions in the 7.0 series drivers
>(which work ok except for that). A detail is that I use FUNCTIONs for
>performing INSERT/UPDATE (as if the FUNCTION was a "stored procedure", that
>does UPDATE or INSERT when appropriate):
>SELECT registerData('my_primary_key', 'a very very long text string')
>Is there a way I can do that using
>PreparedStatement ps = conn.prepareStatement("SELECT registerData(?,?)");
>ps.SetString(2, "a very very very very long string");
>That way I could use a more stable driver with long datasets.
>Is it possible? Are the LOB functions stable?
>Thanks a lot!
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster