Database Tables and Classes

[Anon]

I am considering creating a Class for
each of my database tables. That way
any SQL, for a particular table, will
be contained in its own Class.

Does anybody have any wisdom on this
thought?

LP

[Anon]

Other than long term CM issues regarding code changes when you add or remove tables to your schema, that could be avoided by not specialing for each table.

Also, I would aggree if the code to access the table changed from table to table, but it doesn't, the same same code can be used to access every table, so I don't really know what you gain. A more logical (TO ME) is to make a generic table object for accessing tables.

Warm Regards,

Sheppard Norfleet

[Anon]

It seems like you'd be adding extra work...unless I misunderstood what you meant.

Would each class interface with a seperate table? or would it be loaded with the whole table? are you trying to make some kind of abstraction layer?

---John Holmes...