Hello, Gabriele!

That's a great question!  It's funny you mention it.  A few weeks ago, after 
the light bulb came on in my head when I discovered how EASY it is to connect 
to separate REBOL processes through a port, I started fooling around writing 
a VERY basic DBMS engine in REBOL that could be accessed through a port, 
similar to the way MDBMS can.

I spent about a week on it, off and on, before I got swamped with other 
stuff.  I was able to get the engine to be able to:

*Initialize an object (representing a table) for each .db file it found in a 
directory.

* Accept client requests for add, change, delete, and find and return the 
result set in the form of a block.

The client request had to be in the form of a block (ex):

[Add player "Montana" "Joe" "QB" "SF"]

That was about as far as I got, but, man, I had a lot of fun working on it 
and it was SO cool to think I was actually writing a DB engine (albeit a very 
crude, simplistic one).

Anyway, I'll quit rambling and get back to your question.  What would I like 
to see in a DBMS?  Well, just off the top of my head:

*Normal stuff like adds, deletes, changes, selects (queries).
*Joins.
*Multi-user (locking, etc.)
*Referential Integrity.
*Ability to connect to remote dbs via TCP/IP.

What is not so important to me:

* Transactions
* Triggers or stored procedures (although they would be nice :)  )

Well, I haven't had my morning coffee yet, so that's all I can think of right 
now.  If you pull something like this off, I think it would be HUGE for the 
Rebol community.

Jamey.


On Friday 08 December 2000 04:03, you wrote:
> Hello Jamey!
>
> On 07-Dic-00, you wrote:
>
> [...]
>
> Just a question for you all: would you be interested in a DBMS
> written in REBOL? What kind of functionality do you consider most
> important?
>
> I have some ideas floating in my mind, but I think I won't have
> enough time to implement them all. But perhaps, with some help...
>
> Regards,
>     Gabriele.
-- 
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the 
subject, without the quotes.

Reply via email to