Re: deductive databases
Date: Sat, 14 May 2005 03:59:23 GMT
Message-ID: <vIehe.2018$E7.1642_at_news-server.bigpond.net.au>
"Kenneth Downs" <knode.wants.this_at_see.sigblock> wrote in message
news:tuuel2-uph.ln1_at_pluto.downsfam.net...
> mountain man wrote:
>
>> "Alfredo Novoa" <alfredo_novoa_at_hotmail.com> wrote in message
>> news:87t881l00onh3tibjbqvokll34kn2d67s9_at_4ax.com...
>>
>>> To say that recursion is not useful to solve part explosion problems
>>> shows profound ignorance.
>>
>>
>> 1) WTF is this critical inventory explosion problem?
>
> A widget is made of components. Each component is made of other
> components,
> and so on and so on. The nesting level is not defined ahead of time and
> can go to arbitrary depths.
Throw the max depth code into an automated exception alert to present on a queue to some workgroup that an instance has arisen where widget_id 123456789 has exceeded max depth.
> Building a flat list of a complete parts explosion for an item therefore
> is
> a hassle.
If you dont know the depth it is, but you build a tool to determine the maximim depth first.
>> 2) How many organisations are experiencing this problem?
>>
>
> All manufacturers in the world?
If you relied upon theory you'd have a problem. Fortunately there are viable practice-based alternatives in SQL.
Pete Brown
Falls Creek
Oz
www.mountainman.com.au
Received on Sat May 14 2005 - 05:59:23 CEST