Hello Robert,
a good moment to clear things up:
* Of course, compliance with an ISO-SQL standard is of minimal
importance -- I just grabbed it from the docs.
* The same holds (in a somewhat weaker way) for Java -- I would even
prefer the more general notion type instead of OO, but I am asking in
interest of a CS professor I worked for in the past, who is looking for
impressive demos of non standard DBMS technology. The students might
find resemblance to Java helpful, who knows?
* In this regard it is of interest in how far there are principal
efficiency problems with the support of (deeply nested) object like
structure by the backend, or if the backend may be expected to do this
job not terribly worse then more specialized OODMS -- of course, I would
be interested in any discussions of these topics...
* The same question for doing rule bases on top of the PostgreSQL backend...
* For teaching at university courses, on the other hand, efficiency
would be of lower interest, so there was an idea that there might be
some (possibly toy example like) efforts to tune the frontend into this
direction.
== Academic prototypes, which preferably do not bring too much overhead
for students.
Cheers,
Nick
On 01/31/2011 03:22 PM, Robert Haas wrote:
On Mon, Jan 31, 2011 at 3:32 AM, Jörg Roman Rudnick
<joerg.rudn...@t-online.de> wrote:
* are there any people / projects known which are interested in ORDBMS /
OODBMS usage of PostgreSQL? Strict SQL standard conformance is less
important than the possibility to provide instructive and impressive
examples to students.
* are there any people / projects known which are interested in extending
PostgreSQL at a higher level (plpgsql, creating operators, etc.) for the
sake of ORDBMS / OODBMS functionality?
* are there any people / projects known which are interested in extending
PostgreSQL on the level of developing C code for the sake of ORDBMS / OODBMS
functionality?
* in how far does the backend support such efforts -- would it do fine, or
is rather to be expected that doing ORDBMS / OODBMS driven queries would
lead to disastrous performance?
* are there any people / projects known which are interested in using the
rule (?trigger?) system of PostgreSQL (maybe with extensions) to achieve
some kind of rule base / datalog type inference engines? In how far does the
backend constrain this in regard of performance?
I don't really know much about ORDBMS / OODBMS functionality; a quick
Google search suggests that SQL/OLB is mostly about Java language
bindings, and there's a separate project (pgsql-jdbc) which works on
PostgreSQL connectivity for Java. As far as changes to the core
database are concerned, user-defined functions and operators are not
hard to create, but I'm fuzzy on what specifically you want to do.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
