Building a better hamburger
I’m still working on the Liberty Database. Right now, I’m trying to tie together food processing in the galley. I have my materials list, but trying to get a hamburger to equal beef+bun+lettuce+tomato+ketchup+mustard is being more of a trick than I had hoped for. I’m trying to avoid a full on MRP system, but I do want to grasp in my head how to get there.
It’s not raining here right now. It’s a weird storm…. not like most Southern California ones. On and off showers, not a constant blast of rain like I’m used to. Very irritating, because I had to cancel the Whale Watching trip for today too.
March 13th, 2006 at 6:14 am
OK, you’re trying to quantify a burger in a database? Be aware that whenever someone around here tries to call me a geek, I’m pointing them to this post.
March 13th, 2006 at 6:39 am
It’s practice! Practice, I swear!
And I haven’t been able to get it to work yet either. When it’s working right, then I’ll be geeky enough.
In my defense, what’s the difference between a hamburger, a car or a door?
Oh, and I still have to solve the problem of: Does a
cheeseburger = hamburger + cheese
or
cheeseburger= cheese + beef patty + bun + lettuce + tomato + ketchup + mustard +….
I really want to know how to do the first way, but I have a decent idea how to do the second one. I’m just not there yet on either.
March 13th, 2006 at 7:08 pm
When in doubt about comestibles, retreat to MIL spec:
http://www.dscp.dla.mil/subs/support/specs/mil/44072.pdf
March 14th, 2006 at 8:15 am
Dude… the first solution is seriously how this ENTIRE project (the one I’ve been working on for the last nine months) is panning out for me. My solution is to treat rows as objects and in the UI allow them to point anywhere. GUID’s are my friend.
I know anybody who’s a DB admin probably cringed right now… but seriously, how else are you supposed to represent tree or map structures in SQL?
March 14th, 2006 at 3:32 pm
Dane: No idea… I’m dealing in FileMaker, not SQL, but it’s all relational databasing, right?
As for how far back to trace raw materials, I don’t want to care. I’d rather say:
Finished good has Part Number 1001
Component A has Part Number 1002
Component B has Part Number 1003
Subassembly A1 has Part Number 1004
Subassembly A2 has Part Number 1005
Subassembly B1 has Part Number 1006
Subassembly B1 also uses Part Number 1005
They should all be part numbers, and be allowed to refer to other PN’s, just not itself (no circular parts!)
March 14th, 2006 at 8:12 pm
Actually, a cheeseburger=bun+beef+beef+cheese+cheese+cheese+bacon+avocado
+lettuce+tomato+onion+ketchup+mustard
March 15th, 2006 at 10:47 am
True, but I have to start from basic beginings, and not even worry about eating such a large handful until I can deal with a junior sized meal.
March 16th, 2006 at 11:27 am
Sorry, that was a rhetorical question… that is, unless you actually had an answer.
If you’re still having problems with this email me… I’ve been working with systems similar to this for almost a year now… though not your flavor of RD… RDs are RDs IMHO.