Hi qball,
my "nth degree" is something like that:
Presentation Layer (GUI)
---------------------------------
Business Logic
---------------------------------
Data Access
I think, that it's quite simple. The idea of 3D architecture is to separate orthogonal aspects of aplication. The problem is implementing business logic in terms of objects, e.g.
public class Person
{
string name;
string address;
string phone;
string email;
public Person(string _name, string _address)
{
...
}
...
}
public class Customer: Person
{
ArrayList preferences = new ArrayList();
...
}
If you implement business objects (sometimes called entity objects) you will have to make it persistent. O/R mapping tools gives you possibility to implement your business logic without SQL. You can then use inheritance, polymorphism, N:M relationships.
Of course, you should create a database to store your business objects, but your application can be free of SQL code.
It's not so abstract. I think, that the "rubber is very close to the road".
If you want to think of SQL objects?
Something like: Relation, Column, Constraint?
Maybe: Command, Resultset, Connection?
These objects aren't persistent. Probably they are not business objects. O/R mapping tools are not about it.
Gicio,
Your welcome. Polska not dead yet. Would you like to try eval?
Jacek
Linear Mode
