Re: PL/java - Mailing list pgsql-general

From Rob Sargent
Subject Re: PL/java
Date
Msg-id d96d65f6-f375-b872-3c23-6589bc3c0269@gmail.com
Whole thread Raw
In response to Re: PL/java  (Martin Gainty <mgainty@hotmail.com>)
Responses Re: PL/java
List pgsql-general


On 12/7/20 3:10 PM, Martin Gainty wrote:
P {margin-top:0;margin-bottom:0;}
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

If I'm tracking correctly I can say the java implementation of CopyManager is, to me, blindingly fast.  So if the E and the T are in java then certainly the L can be also.  I have not compared it to straight file-base copy because my data is conceived in Java and slammed home directly from the app (middle-ware). I write relatively large blocks (millions of records) to naked temporary tables and then let straight sql read from there and insert into final tables in chunks.
Un Saludo
m


From: Rob Sargent <robjsargent@gmail.com>
Sent: Monday, December 7, 2020 11:16 AM
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.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.


pgsql-general by date:

Previous
From: Martin Gainty
Date:
Subject: Re: PL/java
Next
From: Ron
Date:
Subject: Re: Deferrable FK not behaving as expected.