References: <56945E0E.3000104@hogranch.com> <56945EA8.9090505@anastigmatix.net> <56946D05.9050508@anastigmatix.net> <5698E79E.6040904@hogranch.com> <56990F46.2000309@anastigmatix.net> <569948F9.9030603@hogranch.com> <56994A59.9050000@anastigmatix.net> From: John R Pierce Message-ID: <569978AA.9030207@hogranch.com> Date: Fri, 15 Jan 2016 14:54:34 -0800 MIME-Version: 1.0 In-Reply-To: <56994A59.9050000@anastigmatix.net> Subject: Re: [Pljava-dev] built, now how to install? Content-Type: text/plain; charset="us-ascii"; Format="flowed" On 1/15/2016 11:36 AM, Chapman Flack wrote: > On 01/15/2016 02:31 PM, John R Pierce wrote: > >> >CONTEXT: SQL statement "CREATE OR REPLACE FUNCTION >> >javatest.complex_send(javatest.complex) RETURNS bytea LANGUAGE java >> >IMMUTABLE RETURNS NULL ON NULL INPUT AS >> >'UDT[org.postgresql.pljava.example.annotation.ComplexScalar] SEND'" >> >ERROR: requested character too large for encoding: 256 > Erk, that's not anything I was expecting. Not even sure what > encoding it's talking about in a function involving no strings. > I'll look tonight. ok, upon some further testing, it only does this if the ENCODING is SQL_ASCII, its fine if the server_encoding is UTF8 but the lc_collation/ctype are 'C'. I note there's a almost 1 second delay between that CONTEXT and that ERROR, suggesting the error is NOT in that CREATE OR REPLACE FUNCTION. I tried setting log_statement = 'all' but just got... < 2016-01-15 14:47:01.895 PST >ERROR: requested character too large for encoding: 256 < 2016-01-15 14:47:01.895 PST >STATEMENT: SELECT sqlj.install_jar('file:///home/piercej/pljava/pljava-examples/target/pljava-examples-1.5.0-SNAPSHOT.jar','examples', true); -- john r pierce, recycling bits in santa cruz _______________________________________________ Pljava-dev mailing list Pljava-dev@lists.pgfoundry.org http://lists.pgfoundry.org/mailman/listinfo/pljava-dev