leblankenship
Programmer
I'm still getting myself to the point where I'm completely confident in my OOP design skills so I'm looking for some feedback on a couple of different ideas and the best approach.
I have an imaging app I'm working on for work with the following hierarchical structure:
A batch of documents gets scanned and stored in the database.
I want to have the scanned documents associated with the batch.
No problem, I have a batch and document table tied together in the database.
At first I tried doing a batch with a document collection but the performance stunk, so I switched to a batch document property which is essentially an object with seperate methods for loading, updating, deleting, and importing information into the list of documents. Since it's exposed to the outside world as a data table and works like a data table otherwise, I believe I can use it with a data repeater without difficulty and be able to manipulate it without difficulty and not run into the overhead of the collection approach. Any problems with this?
I have an imaging app I'm working on for work with the following hierarchical structure:
A batch of documents gets scanned and stored in the database.
I want to have the scanned documents associated with the batch.
No problem, I have a batch and document table tied together in the database.
At first I tried doing a batch with a document collection but the performance stunk, so I switched to a batch document property which is essentially an object with seperate methods for loading, updating, deleting, and importing information into the list of documents. Since it's exposed to the outside world as a data table and works like a data table otherwise, I believe I can use it with a data repeater without difficulty and be able to manipulate it without difficulty and not run into the overhead of the collection approach. Any problems with this?