Just to add my bit to this:
Although I haven't looked into it yet, but I've come across a book
describing how to use CORBA with Java, and JDBC. I'm going to try to get
this book, and see how this could work.
On Fri, 13 Nov 1998, Michael Robinson wrote:
> With the initial positive response, I dived into the CORBA spec, the
> ORBit source, and the PostgreSQL source. I have good news to report.
>
> - CORBA and PostgreSQL were made for each other. The designers of the CORBA
> architecture had object oriented databases (OODB) in mind as one of the
> standard implementation of objects. E.g.:
>
> "An ORB may have access to multiple Interface Repositories. This may occur
> because...an object implementation (such as an OODB) prefers to provide
> its own type information..."
>
> So, implementing CORBA for PostgreSQL is simply a matter of following the
> very clearly designed architecture.
>
> - CORBA is extremely modular with well-defined interfaces between components.
> This means that it should be possible to write generic CORBA glue for
> PostgreSQL that could work with any ORB.
>
> - The ORBit sources appear to be LGPL'ed, which means they can be linked to
> PostgreSQL without poisoning the BSD license.
>
> I also have bad news to report.
>
> - Most of the CORBA functionality that PostgreSQL would rely on is currently
> unimplemented in ORBit.
>
> - While CORBA provides a very disciplined interface for allowing different
> object implementations (e.g. Python and PostgreSQL) to share the same address
> space and execution context safely and efficiently, the PostgreSQL backend
> doesn't seem ready for it. In particular, it doesn't appear to be thread
> safe. It may not even be reentrant, from what I can tell. And, if a backend
> process is not punctual about reading cache synchronization messages out of
> the IPC queue, it appears that excessive cache invalidation would hurt
> performance.
>
> -Michael Robinson
>
>
--
Peter Mount, IT Section
petermount@it.maidstone.gov.uk
Anything I write here are my own views, and cannot be taken as being the
official words of Maidstone Borough Council