How do you think about OODBMS in .NET system?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

FU.U.NA - 30 Apr 2004 21:27 GMT

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?

Reply to this Message

William Ryan eMVP - 01 May 2004 16:07 GMT

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.

> Hi.
>
[quoted text clipped - 24 lines]
> How do you think about OODBMS in .NET system?
> Is there good solution about this?

Reply to this Message

F176 - 13 May 2004 17:30 GMT

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.

> 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
[quoted text clipped - 27 lines]
> > How do you think about OODBMS in .NET system?
> > Is there good solution about this?

Reply to this Message

Alfredo - 03 May 2004 00:58 GMT

>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.

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.

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.

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.

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.

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?

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

>Is there good solution about this?

Not yet :(

Regards
Alfredo

Reply to this Message

F176 - 13 May 2004 17:11 GMT

Thank you for your reply and interest.

> >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
[quoted text clipped - 39 lines]
> Regards
> Alfredo

Reply to this Message

How do you think about OODBMS in .NET system?

Free Magazines