pg.ddx.io  pgsql-pkg-debian@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chapman Flack <chap@anastigmatix.net>
To: Christoph Berg <myon@debian.org>
To: pgsql-pkg-debian@postgresql.org
Subject: Re: PL/Java 1.5.1_BETA2
Date: Sun, 16 Sep 2018 18:12:41 -0400
Message-ID: <5B9ED559.5080208@anastigmatix.net> (raw)
In-Reply-To: <20180916202733.GB30681@msg.df7cb.de>
References: <5B96B226.2080803@anastigmatix.net>
	<20180915203221.GA19015@msg.df7cb.de>
	<5B9D73A2.2090402@anastigmatix.net>
	<20180916201808.GA30681@msg.df7cb.de>
	<20180916202733.GB30681@msg.df7cb.de>

On 09/16/18 16:27, Christoph Berg wrote:

>> 20:07:07 CONTEXT:  SQL statement "SELECT javatest.assertHasValues( CAST('(1,2)' AS javatest.complextuple), 1, 2)"

Yup, ComplexTuple again....


> 20:06:38 CONTEXT:  SQL statement "SELECT javatest.assertHasValues(CAST('(1,2)' AS point), 1, 2)"

Point this time. Sigh. Same issue.

Instead of the silly boot functions, I should probably add to PL/Java a way
to request a CommandCounterIncrement, and have install_jar always use it,
after loading the jar, before running the DDR commands.

> Also, does it have to be that verbose all the time, even if things
> worked?

I don't have very good control yet. There's a page on the wiki for
how I *want* the logging to work:

  https://github.com/tada/pljava/wiki/Thoughts-on-logging

... and I also want, eventually, the testing to happen in a more
standard way, such as TAP (tap4j and pgtap). But those goals still
need a substantial development effort. For now, I am stuck with one
example function that writes verbose log messages, and using INFO
for the succeeding ones and WARNING for the failing ones. And even
different PostgreSQL versions have different amounts of verbose
logging that they do for CREATE TYPE commands, etc.

> 20:22:25 Exception in thread "main" java.lang.ClassCastException: sun.org.mozilla.javascript.ConsString cannot be cast to java.lang.String

Could you try changing pljava-packaging/build.xml at line 353 from

computedPath = replacement + computedPath.slice(plen);

to

computedPath = new java.lang.String(replacement + computedPath.slice(plen));

I keep being surprised by differences in the JavaScript interpreter
supplied in different Java runtimes; the unchanged code has worked
without problems on so many. But I *think* this should work on your jdk7
and not break others....

-Chap




view thread (17+ messages)  latest in thread

Message-ID: <5B9ED559.5080208@anastigmatix.net>
Permalink:  ../5B9ED559.5080208@anastigmatix.net/
Also on:    postgresql.org/message-id/5B9ED559.5080208@anastigmatix.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-pkg-debian@postgresql.org
  Cc: chap@anastigmatix.net, myon@debian.org
  Subject: Re: PL/Java 1.5.1_BETA2
  In-Reply-To: <5B9ED559.5080208@anastigmatix.net>
  References: <5B96B226.2080803@anastigmatix.net> <20180915203221.GA19015@msg.df7cb.de> <5B9D73A2.2090402@anastigmatix.net> <20180916201808.GA30681@msg.df7cb.de> <20180916202733.GB30681@msg.df7cb.de> <5B9ED559.5080208@anastigmatix.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox