Re: I think that relational DBs are dead. See link to my article inside

Dmitry Shuklin wrote:
> Hi Cimode,
>
> > What other similar models are you refering to?
>
> graphs theory, semantic network, frames, neural networks, hierarchical
> semantic network, M-Network.
>
> > > Of course. Just need to create yet anoter .NET class.
> > All right..What kind of operations are currently supported over neurons
> > data type?
>
> Here is very important issue. I make this DB for neural networks but i
> don't include any sample neuron implementation into kernel. Neuron
> models can be implemented in separate DLLs and attached to DB.
>
> For example i describe one of neuron model which i am using.
>
> - adding link to another neuron
> - removing link to another neuron
> - scan all input neurones and compute neuron state.
> - put current state to output linked neurones
>
> all them are just a methods, implemented in class. when some neuron
> receives thread (message) it can invoke some menthods from related
> neurons. I have a brief articles on russian about neural network models
> which i am using. briefly them equivalent to finite state grammar and
> can be used to parse natural language (russian).
I believe this is a description of the computational operations your system can perform on a specific implementation.

> and there no specific neuron data type. there exists a set of
> interfaces. some interfaces are mandatory for each neuron, some not.
> there are many neuron types in one network. but all can communicate
> with each other via interfaces.
If you don't define a data type neuron what are the characteristics of a *neuron*?

> Here links to my old english articles. But they are not about this DB.
>
> http://www.shuklin.com/ai/ht/en/ai04001f.aspx
> http://www.shuklin.com/ai/ht/en/ai00002f.pdf
> http://www.shuklin.com/ai/ht/en/ai00007f.pdf
> http://www.shuklin.com/ai/ht/en/ai00009f.pdf
>
>
> > By operations I mean operators that can be applied to data of neuron
> > data type...
>
> they completly defined by developer as class methods
You should note that RM allows to associate in a one-shot declarative manner all operators and constraints over values that can be applied to a specific ensemble of value. Based on your description (interfaces), it seem that all equivalent need to be specified programmatically at run time in a recurring manner. I doubt this constitutes a progress...

> > Can you for instance apply equal operator to state that 2 neurons are
> > equal?
>
> 1.yes,
How?
> 2. models which i am using don't need this feature
So you are stating that the sample data you are using for testing determine how sound is an abstract model?

> > Can you find all neurons that fit a particular description, 2 particular description...
>
> 1.yes, O(N) in current version
> 2. models which i am using don't need this feature
Keep in mind that RM abstract level allows to dissociate this kind of issue from particular context...Once you declare a data type neurons and define all its attributes you can image all search combination of attribute conditions.

> > How do you find for instance ALL neurons that
> > have a specific wavelength but not a particular configuration (assuming
> > wavelength and configuration being properties applyable of neuron)?
>
> You should scan collection of neurunes and invoke some methods from
> neurones. Then decide what you want to do with each instance.
What if you have 2 users doing the same thing over 3 trillions neurons, who has priority? how is parallelism handled? throughput? Are the IO accesses liner, bidimensional, direct image? How about RAM?

> > How do you support read consistency...
>
> It is single user OODB. Let say that this question is open
Then it is a single application developped on a single post not a real server yet. A DBMS important ability is to behave like a server for requests...

> > For instance what happens when
> > you begin a insert transaction with committing over a table then run a
> > select over the same table...What kind of version of the table does you
> > select return?
>
> there are no tables as they are in RDB. and no inserts. and no selects.
> as conceptions equivalent to RDB.
No inserts? no update? How do you keep track of your data? How do you update it?

> there are collections - collections are instances of objects too
> you can create instance. find instance. destroy instance.
> you can add existing instance into collection. one instance can be
> added to different collections.
>
> if you start transaction, and add some instance to some collection then
> collection is marked as changed by this transaction. you will receive
> new version of collection instance. collections stores only pointers.
How about another user coming in? what version of data will he/she get?

> no data. objects stores only methods. no data. attributes some times
No data? I will use information instead... Are you saying the system is meant to work only once? Where do you store past information? How do you retrieve that past information?

> are scalar objects. but they not parent objects. each node can have
> many versions. anymore the same attriburte can belong to different
> instances.
>
>
> > This kind of segregation is done at compile time which
> > saves resources...
>
> In current version i support only runtime constraints. no declarative
> style. only imperative.
> In future - will see in future.
It seems to me you still have a long way to go before saying relational is dead?
I will buy you a copy when done...

> > I do not know C# but I have complied classes in VB DOT NET. Running it
> > is one thing but making it a DBMS is another thing.
>
> now it is the same ))
>
> WBR,
> Dmitry
Received on Wed Jul 05 2006 - 10:43:08 CEST