From: | David Goodenough <david(dot)goodenough(at)btconnect(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: PL/java |
Date: | 2020-12-08 10:46:28 |
Message-ID: | 4280243.LvFx2qVVIh@continuum |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
As of Java-16 there is a replacement for JNI which allows direct calling of native interfaces
without the need for hand coded stub code.
On Monday, 7 December 2020 22:10:01 GMT Martin Gainty wrote:
> Nota Bene:
> Almost all official interfaces to/from Oracle are coded in Java
> FWIK google's implementations are 95% python
> (although you would need to understand JSON formatting for import/export
> requirements) for those reasons i tread lightly before disparaging either
> language
>
> Going Forward:
> try to implement PL/SQL that rob/joshua mentioned
> if you're calling no-joy after implementing PL/SQL
> then we can take a look at interfacing to Postgres ETL binaries with a JNI
> interface provided the JNI is spot on with signatures for each referenced
> function
>
> Un Saludo
> m
>
> ________________________________
> From: Rob Sargent <robjsargent(at)gmail(dot)com>
> Sent: Monday, December 7, 2020 11:16 AM
> To: pgsql-general(at)lists(dot)postgresql(dot)org <pgsql-general(at)lists(dot)postgresql(dot)org>
> Subject: Re: PL/java
>
> On 12/7/20 8:25 AM, Adrian Klaver wrote:
> > On 12/7/20 7:18 AM, Hemil Ruparel wrote:
> >> I want to say this. I never liked any extension language. It's like
> >> Java is not meant to interact with databases.
> >
> > The JDBC folks might disagree.
>
> That interaction is strictly sql to db, data to app. As it should be.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2020-12-08 11:23:43 | Re: PL/java |
Previous Message | Aravindhan Krishnan | 2020-12-08 08:18:33 | Re: postgres-10 with FIPS |