Andy Colson wrote:
> On 4/15/2010 11:59 AM, John R Pierce wrote:
>> The tarball for 64bit 8.4.3 on Solaris Sparc is missing some ./pgxs/...
>> files I seem to need to build pl/java. they exist in the 32bit version
>> but at least of them, Makefile.global, appears quite build specific.
>>
>
> So, it seem to be painful to compile the java stuff... and upthread
> you said someone "was more comfortable with java" and they were doing
> "some sorta-statistical calculations"... is it really worth all that?
>
> They could do it in perl and it would probably be just as fast. I
> mean, they arent gonna write _that_ much stored procedure code, are they?
>
> If they had questions there are several on this list that could help
> them convert java to perl.
>
> I'm just wondering... which is more expensive?
>
> 1) painful install pl/java, develop SP
> 2) install pl/perl, painful develop SP
They have their code running now in pl/java on a Windows dev platform.
but the production database this is targeted at is Solaris/Sparc
in fact, the *original* SP was in plsql on an Oracle database, but it
made use of some oracle features which are not in Postgres, something
called "Oracle Pipelined Table" (I don't even know what this is).
if it was me writing the code, I'd be doing it in perl, no problem.
Their attitude is, pljava and SQLJ are a standard, plperl isn't.
anyways, I've got it all built now, and am just sorting out loading
problems, I've moved over to the pljava-dev list for assistance on my
current problems as this list is failrly java-hostile.
