|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
|||
|
|||
|
Bill of parts?
I am trying to learn more about how to properly design an efficient algorithm for a "bill of parts" where parts are made up of parts which are made up of parts and so on, in which a database has an M:N relationship with itself. If anyone knows of any database design examples, tutorials, etc that I may examine thoroughly that would be very helpful.
|
|
#2
|
||||
|
||||
|
Code:
table.part ID parentID ... |
|
#3
|
|||
|
|||
|
One approach ss to create a hierarchy resembling a family tree.
Part PartID ----- --------- test 1 subtest 1.1 anotherpart 1.2 secondpart 1.1.1 and so on. |
![]() |
| Viewing: Dev Shed Forums > Databases > Database Management > Bill of parts? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|