How do you think about OODBMS in .NET system?

  • Thread starter Thread starter FU.U.NA
  • Start date Start date
F

FU.U.NA

Hi.

I was finding a simple way to save objective and relational data.
I guessed about SQL Server, but it's too complex and needs more codes
about non-logic.

My data is a game design data, so it is complex model and needs
hierarchy. And also, it contains big (1024x1024) bitmap image data. As
you know, in RDBMS making hierarchy data is most hard work.

I was looked for DB system for my data, and I found some infor about
OODBMS and ORDMBS.
Unfortunatly, ADO.NET designed for RDBMS, using them on .NET is more
harder and expensive then using normal RDBMS.

I don't know well, I thought OODBMS is just a memory object model that
can be stored, and some management system.

So I thought .NET basic object system + .NET serialization + some
custom manager object will work like OODBMS.
But as I experienced, .NET serialization was so slow without any
specific reason. Especially for complex hierarchy model.

..NET serialization seems using much time for calculating object
hierarchy.


How do you think about OODBMS in .NET system?
Is there good solution about this?
 
ORM is a very good solution. Check out Deklarit's product, www.deklarit.com
(which is much more than a ORM Tool), I think it might help you out
immensely. I've used the product quite a bit and it's as good as they get.
 
I was finding a simple way to save objective and relational data.
I guessed about SQL Server, but it's too complex and needs more codes
about non-logic.
Click to expand...

And it is not relational, unfortunately.
My data is a game design data, so it is complex model and needs
hierarchy. And also, it contains big (1024x1024) bitmap image data. As
you know, in RDBMS making hierarchy data is most hard work.
Click to expand...

It is not, but in SQL DBMS it is.
I don't know well, I thought OODBMS is just a memory object model that
can be stored, and some management system.
Click to expand...

OODBMS is a return to the Network DBMS with some OO features. A
backward step and a resounding market failure in the 90's.

The market share of OODBMS is in continuous decrease.
So I thought .NET basic object system + .NET serialization + some
custom manager object will work like OODBMS.
Click to expand...

It could be enough for what you want.
But as I experienced, .NET serialization was so slow without any
specific reason. Especially for complex hierarchy model.
Click to expand...

But it is very easy to create your own serialization classes. .NET
serialization is also terribly ineficient with disk space even if you
use the binary format.
How do you think about OODBMS in .NET system?
Click to expand...

It could be useful for some very special circumstances while we wait
for a truly RDBMS.
Is there good solution about this?
Click to expand...

Not yet :(


Regards
Alfredo
 
Thank you for your reply and interest.



Alfredo said:
And it is not relational, unfortunately.


It is not, but in SQL DBMS it is.


OODBMS is a return to the Network DBMS with some OO features. A
backward step and a resounding market failure in the 90's.

The market share of OODBMS is in continuous decrease.


It could be enough for what you want.


But it is very easy to create your own serialization classes. .NET
serialization is also terribly ineficient with disk space even if you
use the binary format.


It could be useful for some very special circumstances while we wait
for a truly RDBMS.


Not yet :(


Regards
Alfredo
Click to expand...
 
I think this is just what I have been found. (OODBMS for .NET environment.)
I'm downloading trial version, I hope this product supports simple and
eventual classes.
Thank you for your reply.
 
Back
Top