Re: Introducing PlayDB (The Model, The Language, The DBMS)

In article <ba87a3cf.0310091131.2bd3b6e7_at_posting.google.com>, Seun Osewa
>Seun Osewa
>PS: I would post a follow-up to this e-mail once google groups users
>can see it.

Hi,

The architecture I have been thinking of involves storing both the data and the business logic on the server. "Users" never actually use the query language (Let's call it PL/PlayQL, which would be procedural) directly. They instead connect to the PL/PlayQL programs running on the server, via a simple request/response interface.

The language, while strictly procedural, would include a savepoints feature that will allow the server to roll back execution in the case of mysterious errors and try again from last savepoint. SO the effects of program execution can always be reversed until a savepoint. And because the program is managed by the server the programs do not stop running abruptly when clients disconnect. In fact one can have long-running processes on the server and it becomes something like an OS (pending: unfuzzification of these statements).

Summary: processes using "PL/PlayQL" running on database server having flexible access to data. Client programs connect to these processes and communicate using simplified protocols that are totally independent of the underlying database. All business logic is implemented on the server. PL/PlayQL as a language implements savepoints and can be rolled back to last savepoint. Communication with client actually takes place at savepoint boundaries (cause it cannot be reversed).

Seun Osewa

• Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web ----- http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups NewsOne.Net prohibits users from posting spam. If this or other posts made through NewsOne.Net violate posting guidelines, email abuse_at_newsone.net