Re: TODO list: Allow Java server-side programming

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Peter Mount <peter(at)retep(dot)org(dot)uk>
Cc: Alex Pilosov <alex(at)pilosoft(dot)com>, tomasz konefal <twkonefal(at)yahoo(dot)ca>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO list: Allow Java server-side programming
Date: 2001-02-04 09:18:09
Message-ID: 3A7D1E51.E383AB7F@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Mount wrote:
>
> At 14:57 02/02/01 -0500, Alex Pilosov wrote:
> >On Fri, 2 Feb 2001, tomasz konefal wrote:
> >
> > > could someone please clarify what "Allow Java
> > > server-side programming" actually means? what are the
> > > limitations of using java and jdbc with pgsql?
> >
> >It means to embed Java interpreter inside postgres, and allow writing
> >stored procedures and triggers in Java.
>
> Thats correct. Basically you are talking of something like PL/Java. The
> Java side would be simple, but its linking the JVM to the backend that's
> the problem.
>
> It's been a while since I delved into the backend, but unless it's changed
> from fork() to threading,

Someone posted here recently his port/tweaks of backend so that it used
threads instead of fork(). IIRC it was done to be used inside a java
client in an embedded system.

----------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-02-04 09:26:48 Re: Like vs '=' bug with indexing
Previous Message Bruce Momjian 2001-02-04 05:55:30 Reminder about Announce/General lists