Re: In an RDBMS, what does "Data" mean?

Anthony W. Youngman wrote:

[snip]
> Chopping up is just as easy in MV. The difference is, (a) you're not
> required to do it to get the data IN to the database, and (b) if you've
> done it properly, the database will do it for you when you want to get
> the data OUT.

Magic! Yey!

>> Now, I also want one listing for the measurements of stock turnaround,
>> in order to aim for just-in-time logistics and optimally sized orders. 
>> In an RDBMS I would create another view on the same schema. Would, in 
>> MV, another portal be the way to approach this?

Ask Dawn. I was trying to figure out what a portal is.

> To get the invoice data
> LIST INVOICES BY _at_ID field-names
>
> and to get a listing of what's shipped grouped by stock code
> LIST INVOICES BY.EXP STOCK-CODE field-names.
>
> In other words, I've just changed the sort criteria from the primary
> single-valued invoice number to the multi-valued stock code, and the db
> will chuck a different view of the data at me.

The logistic manager is not iterested in INVOICES. Why do you bother her with INVOICES? She wants to see SHELVES, WAREHOUSES, ORDERQUANTITIES, PACKLISTS (just adapting to your shouting habit ;-) Received on Tue Jun 15 2004 - 02:53:08 CEST