By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,663 Members | 1,455 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,663 IT Pros & Developers. It's quick & easy.

O/R Mapping tool like Apple has.....for .NET?!?!

P: n/a
Hi!

I post this text 1 year ago. But no one really could give
me an answer. This is the text that I posted long time ago:
I have a fundamental question about
The way .NET handles the object orientated way of
Persistence. I am coming from JAVA and WebObjects (Apple)
World and I am looking for a convenient way of working
with objects without seeing any SQL statements only
objects. I have used that approach for years on the
WebObjects Platform (Enterprise Object Framework) and in
Java recently (Container Managed Persistence). I am
looking for something like that in the Microsoft world.

As far as I understand Microsoft does not distinguish
between the Object Model and the Relational Model. The
main difference is that the Object model allows n : m
relationships and the Relational does not allow them. Here
a small example to visualize the problem:

Example:
There is a Patient object with following Attributes

String patientGUID;
String name;
Int age;
Hashtable diseases; (or some other Container like
Collection or Array)
And there is a Disease Object

String diseaseGUID;
String name;
In the object Model there is relation between Patient and
Disease where the patient has his diseases but on the
other site one disease can belong to 1..* patients. (n :
m)

That n : m relationship can not exist within a relational
database without a link table that contains the
connections between the tables: Patient and Disease.

Now, I would like to connect the object Model containing
TWO Entities (Patient, Disease) with the relational
database (containing THREE tables). Then I want to work
with my objects; e.g. create new diseases connect them to
existing patients by putting the diseases into the array
or create new Patients and connect them with already
existing diseases or just change a Patients name. When I
am finished I just want to say SAVECHANGES and the
database is updated accordingly including all link table
entries.

So all I have to care about are my objects and the
relations between them, some invisible layer does all the
dirty work like building SQL, converting the data types
and caching. So if I fetch a Patient with a specified GUID
I do not have to care about fetching his diseases. They
are fetched automatically. If there are too many Diseases
I do not care some kind of algorithm handles that problem
in such a way that if I have to search all of them for
something they are simply there. They are loaded on demand
(lazy evaluation)

Supposing that the disease has a further connection with
some DiseaseType Object/Table and that table has an
attribute/column "Description" I can access it by typing
the following code:

TextField1.Text = currentDisease.type().description()

Please note that to retrieve the description value I did
only fetch the Patient. The diseases and its types were
fetched automatically.

Is something like that possible or am I excepting too much
of the .NET?

-------------------------------------------------------------------


This tool should be a mixture between Microsoft Visio (I mean ORM modelling)
and a good object-to-relational mapping tool.

Is something like that NOW available????
thx!
gicio
Nov 20 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Hi,

Is this what you are looking for? http://www.softwire.com/

Ken
-------------------------
<gi***@web.de> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hi!

I post this text 1 year ago. But no one really could give
me an answer. This is the text that I posted long time ago:
I have a fundamental question about
The way .NET handles the object orientated way of
Persistence. I am coming from JAVA and WebObjects (Apple)
World and I am looking for a convenient way of working
with objects without seeing any SQL statements only
objects. I have used that approach for years on the
WebObjects Platform (Enterprise Object Framework) and in
Java recently (Container Managed Persistence). I am
looking for something like that in the Microsoft world.

As far as I understand Microsoft does not distinguish
between the Object Model and the Relational Model. The
main difference is that the Object model allows n : m
relationships and the Relational does not allow them. Here
a small example to visualize the problem:

Example:
There is a Patient object with following Attributes

String patientGUID;
String name;
Int age;
Hashtable diseases; (or some other Container like
Collection or Array)
And there is a Disease Object

String diseaseGUID;
String name;
In the object Model there is relation between Patient and
Disease where the patient has his diseases but on the
other site one disease can belong to 1..* patients. (n :
m)

That n : m relationship can not exist within a relational
database without a link table that contains the
connections between the tables: Patient and Disease.

Now, I would like to connect the object Model containing
TWO Entities (Patient, Disease) with the relational
database (containing THREE tables). Then I want to work
with my objects; e.g. create new diseases connect them to
existing patients by putting the diseases into the array
or create new Patients and connect them with already
existing diseases or just change a Patients name. When I
am finished I just want to say SAVECHANGES and the
database is updated accordingly including all link table
entries.

So all I have to care about are my objects and the
relations between them, some invisible layer does all the
dirty work like building SQL, converting the data types
and caching. So if I fetch a Patient with a specified GUID
I do not have to care about fetching his diseases. They
are fetched automatically. If there are too many Diseases
I do not care some kind of algorithm handles that problem
in such a way that if I have to search all of them for
something they are simply there. They are loaded on demand
(lazy evaluation)

Supposing that the disease has a further connection with
some DiseaseType Object/Table and that table has an
attribute/column "Description" I can access it by typing
the following code:

TextField1.Text = currentDisease.type().description()

Please note that to retrieve the description value I did
only fetch the Patient. The diseases and its types were
fetched automatically.

Is something like that possible or am I excepting too much
of the .NET?

-------------------------------------------------------------------


This tool should be a mixture between Microsoft Visio (I mean ORM modelling) and a good object-to-relational mapping tool.

Is something like that NOW available????
thx!
gicio

Nov 20 '05 #2

P: n/a
Ok !

I checked this site....
and this is not what I am looking for.


gicio


<gi***@web.de> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...
Hi!
I don't know......
http://www.softwire.com/ is down?!?!

gicio

"Ken Tucker" <vb***@bellsouth.net> wrote in message
news:uY*************@TK2MSFTNGP12.phx.gbl...
Hi,

Is this what you are looking for? http://www.softwire.com/

Ken
-------------------------
<gi***@web.de> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hi!

I post this text 1 year ago. But no one really could give
me an answer. This is the text that I posted long time ago:
I have a fundamental question about
The way .NET handles the object orientated way of
Persistence. I am coming from JAVA and WebObjects (Apple)
World and I am looking for a convenient way of working
with objects without seeing any SQL statements only
objects. I have used that approach for years on the
WebObjects Platform (Enterprise Object Framework) and in
Java recently (Container Managed Persistence). I am
looking for something like that in the Microsoft world.

As far as I understand Microsoft does not distinguish
between the Object Model and the Relational Model. The
main difference is that the Object model allows n : m
relationships and the Relational does not allow them. Here
a small example to visualize the problem:

Example:
There is a Patient object with following Attributes

String patientGUID;
String name;
Int age;
Hashtable diseases; (or some other Container like
Collection or Array)
And there is a Disease Object

String diseaseGUID;
String name;
In the object Model there is relation between Patient and
Disease where the patient has his diseases but on the
other site one disease can belong to 1..* patients. (n :
m)

That n : m relationship can not exist within a relational
database without a link table that contains the
connections between the tables: Patient and Disease.

Now, I would like to connect the object Model containing
TWO Entities (Patient, Disease) with the relational
database (containing THREE tables). Then I want to work
with my objects; e.g. create new diseases connect them to
existing patients by putting the diseases into the array
or create new Patients and connect them with already
existing diseases or just change a Patients name. When I
am finished I just want to say SAVECHANGES and the
database is updated accordingly including all link table
entries.

So all I have to care about are my objects and the
relations between them, some invisible layer does all the
dirty work like building SQL, converting the data types
and caching. So if I fetch a Patient with a specified GUID
I do not have to care about fetching his diseases. They
are fetched automatically. If there are too many Diseases
I do not care some kind of algorithm handles that problem
in such a way that if I have to search all of them for
something they are simply there. They are loaded on demand
(lazy evaluation)

Supposing that the disease has a further connection with
some DiseaseType Object/Table and that table has an
attribute/column "Description" I can access it by typing
the following code:

TextField1.Text = currentDisease.type().description()

Please note that to retrieve the description value I did
only fetch the Patient. The diseases and its types were
fetched automatically.

Is something like that possible or am I excepting too much
of the .NET?

-------------------------------------------------------------------


This tool should be a mixture between Microsoft Visio (I mean ORM

modelling)
and a good object-to-relational mapping tool.

Is something like that NOW available????
thx!
gicio



Nov 20 '05 #3

P: n/a
hi cor,
i like to use:

C#, VB.NET , C++.NET
(C# is my favorite!!!)
gicio
"Cor" <no*@non.com> wrote in message
news:3f***********************@reader21.wxs.nl...
Gico,
What program language you want to use?
Cor

Nov 20 '05 #4

P: n/a
Cor
Tio,
This is a VB.language group, but there is too a C# group
Almost everything you can do with C# you can do with VB.net
But because that I saw that you are used to that code, maybe its wise to put
the question too in the C# group.

My expirience is that people active in this VB.net group are very practical
and I asume they are less theoretic than the ones in C#.
(Although there are a lot active in both groups and maybe someone active in
this group will take the time to answer your question).
Cor
Nov 20 '05 #5

P: n/a
nGen does everything you're asking for, including the GUIDs. Simply provide
the PatientID, and when you request the Diseases, it will connect to the
database at that time and get them. You can do this in SQL Server with this
structure, which I think you alluded to.

Users
*UserID

Diseases
*DiseaseID

UserDiseases
*UserID
*DiseaseID

It returns to you a list of Dieseases, not a list of UserDiseases, it simply
uses the UserDiseases in the JOIN.

A new beta will be coming out at the end of this week, and will include
support for generating a business layer which inherits from the data layer,
and is used against the UI. At this point you only get the DAL. We're
looking at a C# release for the BLL a few weeks after that.

http://www.nAlliance.com/Products/nGen

KS
<gi***@web.de> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hi!

I post this text 1 year ago. But no one really could give
me an answer. This is the text that I posted long time ago:
I have a fundamental question about
The way .NET handles the object orientated way of
Persistence. I am coming from JAVA and WebObjects (Apple)
World and I am looking for a convenient way of working
with objects without seeing any SQL statements only
objects. I have used that approach for years on the
WebObjects Platform (Enterprise Object Framework) and in
Java recently (Container Managed Persistence). I am
looking for something like that in the Microsoft world.

As far as I understand Microsoft does not distinguish
between the Object Model and the Relational Model. The
main difference is that the Object model allows n : m
relationships and the Relational does not allow them. Here
a small example to visualize the problem:

Example:
There is a Patient object with following Attributes

String patientGUID;
String name;
Int age;
Hashtable diseases; (or some other Container like
Collection or Array)
And there is a Disease Object

String diseaseGUID;
String name;
In the object Model there is relation between Patient and
Disease where the patient has his diseases but on the
other site one disease can belong to 1..* patients. (n :
m)

That n : m relationship can not exist within a relational
database without a link table that contains the
connections between the tables: Patient and Disease.

Now, I would like to connect the object Model containing
TWO Entities (Patient, Disease) with the relational
database (containing THREE tables). Then I want to work
with my objects; e.g. create new diseases connect them to
existing patients by putting the diseases into the array
or create new Patients and connect them with already
existing diseases or just change a Patients name. When I
am finished I just want to say SAVECHANGES and the
database is updated accordingly including all link table
entries.

So all I have to care about are my objects and the
relations between them, some invisible layer does all the
dirty work like building SQL, converting the data types
and caching. So if I fetch a Patient with a specified GUID
I do not have to care about fetching his diseases. They
are fetched automatically. If there are too many Diseases
I do not care some kind of algorithm handles that problem
in such a way that if I have to search all of them for
something they are simply there. They are loaded on demand
(lazy evaluation)

Supposing that the disease has a further connection with
some DiseaseType Object/Table and that table has an
attribute/column "Description" I can access it by typing
the following code:

TextField1.Text = currentDisease.type().description()

Please note that to retrieve the description value I did
only fetch the Patient. The diseases and its types were
fetched automatically.

Is something like that possible or am I excepting too much
of the .NET?

-------------------------------------------------------------------


This tool should be a mixture between Microsoft Visio (I mean ORM modelling) and a good object-to-relational mapping tool.

Is something like that NOW available????
thx!
gicio

Nov 20 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.