Last post Sep 30, 2008 04:21 PM by DkUltra
Sep 30, 2008 01:39 PM|JORGEMAL|LINK
I am developing an application which involves the maintenance of several database tables and I think that defining a class for every table to encapsulate the basic operations (insert, update, delete, find) would be a good idea. So I did that and wrote the
first class for one table that has a record with 2 fields and defined every field as a property; so far it is working just fine. Now that I wm working with the second table I see that it has a record of about 45 fields and so a question arises.
Is it logical or optimal to define 45 properties, one for each field?
Sep 30, 2008 04:21 PM|DkUltra|LINK
Any way to upgrade to vs2008 /.net 3.5 where linq does this for a person ?
a person could use table adapters
Best way--> normalize the table/database reducing field counts.