From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Wim Bertels <wim(dot)bertels(at)khleuven(dot)be> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: naked objects from stored procedures, interface generation |
Date: | 2010-12-23 08:31:41 |
Message-ID: | AANLkTimxB8BrjU5D85fZHZbkzOLPi_79746wufi9tc71@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
I know about one similar project - Garuda, but this project isn't open.
What it does:
* OOP - objects, properties, methods - not based on PostgreSQL OOP
* support of workflow - lifecycle for objects
* support of collection of objects
It was designed in plpgsql with special modules to PHP, where was
possible to work with Garuda objects like PHP objects.
Regards
Pavel Stehule
2010/12/23 Wim Bertels <wim(dot)bertels(at)khleuven(dot)be>:
> Hallo,
>
> there exist many framework that 'backward' engineer from a programming
> language to database to make the data persistent.
> so: code >> db (generated)
> eg. hibernate, turbogears many others
>
> My question is, from db point of view, do we have such frameworks that work
> the other way,
> ie that forward engineer from a database to a user interface (web or
> program),
> maybe using the stored procedures available on the database (eg in the same
> naked objects work)
> so: exisiting db (possible + stored procedures) >> user interface (eg crud
> or other)
>
> mvg,
> Wim
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2010-12-23 08:39:48 | Re: naked objects from stored procedures, interface generation |
Previous Message | Atul Kumar | 2010-12-23 08:31:08 | Issue while using PostgreSql 8.4. |