Would it make sense to implement the PostgreSQL SPI interface as a set
of Parrot PMC's; then ANY HLL on Parrot could use those PMC's? could
the SPI be wrapped by PERL for example, and then the THER HLL's simply
use the classes/objects of the PERL interface?
Message
From: David Fetter [mailto:david (AT) fetter (DOT) org]
Sent: Thursday, July 13, 2006 10:09 AM
To: Parrot Developers
Subject: PL/Parrot
Folks,
I'd like to get some insights into how to implement a PL/Parrot for
PostgreSQL. For those unfamiliar, PostgreSQL is an extensible DBMS
which allows people to plug in procedural languages. I'm thinking
that Parrot could provide a way to plug in lots and lots of
these Perl6 minimal repeated effort.
So far, I have two initial high-level ideas for a design of such a
thing:
* Embedding Parrot in C using PostgreSQL's SPI interface
with
wrappers around the SPI interface for each target language as
appropriate.
* Running Parrot as a separate daemon process with a communication
channel open to PostgreSQL.
If interested, please contact me.
Cheers,
D