Re: Thoughts on Voiding Invoices

["Joshua D. Drake" <..hidden..>]

> Now, what interface do you propose that these function calls and stored
> procedures have? This is what I mean by the API needs to come before the
> data modelling. I guess I'm kind of agreeing with David Tangye that we
> need to set some scope/requirements _before_ we start hacking and
> chopping at the schema.

Everything starts with how the data is stored.


>  The information that
> _needs_ to be on an invoice is pretty much specified by law/GAAP; who
> cares how the system stores that information.

I am sorry but that is a very careless statement.

> What we need to do is
> specify how we are going represent that information at the point where
> we separate the business logic and the display. When I say display I
> mean it in a very general way... It may be the Web interface that's part
> of the project. It might be an XML/EDI document parser/generator. It
> might even be a webstore (Interchange/osCommerce) that has chosen to
> interface directly. Who knows how the API will be used in the future.

Which all starts at the foundation, which is the database, the schema,
and the data.

> 
> I think SQL Ledger not having that very clear separation is a big part
> of what has limited its adoption as a business infrastructure module.
> 

Uhh no there was a lot more to it then that.

Joshua D. Drake



-- 

   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
   Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/