A
Alex Papadimoulis
Hi Bernardo,
Here are my thoughts:
need to make it be ready for any DBMS? Often times, the answer is really no.
Just because there is a remote possibility that perhaps sometime in the
future a later user of the system may just want to make it run on the Atari
2600 ... doesn't mean it's going to happen. And when it does, it is a lot
more work then just switching the "DATABASE-TO-USE" paramater ...
for that. Sometimes DataObject classes are needed, sometimes they're just
simple enough that their not needed. I'd go with just one class that does
the CRUD operations.
Good luck, and dont hesitate asking more ?? !
-- Alex Papadimoulis
Here are my thoughts:
Watchout for the MPTE Trap (Must Port To Everything). Is there a really aI have a class DBObjects that returns the correct ADO.NET object for the
database i´m using, since I want my system to be ready for any DBMS.
need to make it be ready for any DBMS? Often times, the answer is really no.
Just because there is a remote possibility that perhaps sometime in the
future a later user of the system may just want to make it run on the Atari
2600 ... doesn't mean it's going to happen. And when it does, it is a lot
more work then just switching the "DATABASE-TO-USE" paramater ...
Two almost identical classes is just too much code and too complex. No needOr should I have a userDB class that has all the same properties than user
and have the load and write methods for the DataBase and make the user load
and write methods delegate to the user ones???
If so I would have two classes almost identically... What should I
for that. Sometimes DataObject classes are needed, sometimes they're just
simple enough that their not needed. I'd go with just one class that does
the CRUD operations.
Good luck, and dont hesitate asking more ?? !
-- Alex Papadimoulis