Re: i/o module

David Gibbs wrote:

Personally I don't like the idea of making the IO modular ... make the business function modular.

So you call a module to create a order line item ... you pass it a order, item number, quantity, etc, and the order line item is created. You don't know how it was created, but it gives you a line item reference.

If you write the function using regular database IO initially, you can change it to use sql if need be (make sure the 'need' is real and not just to use SQL) and the caller of the function doesn't need to know.

This is definitely the better solution. This provides innumerable benefits, not the least significant of which is the ability to change the layout of your database - or even its location. Take an order history routine. It can return orders from as far back as you have history. However, some of it could be in online storage, some in slower nearline storage. The caller doesn't care; they just want a list of orders.

Joe