1) Larry peakgreen wants to store information for his landscaping service. Larry

Question

1) Larry peakgreen wants to store information for his landscaping service. Larry needs to track the common and latin names for each plant. Also, he wants to store standard wholesale and retail prices for each plant. For trees, the database should track the tree's height and caliper (trunk diameter). Some plants are classified as shrubs. For these plants, Larry wants the database to store the size (in gallons), the planting distance between plants ( in inches), and whether the shrub is flowering or non-flowering. the databse will include other types of plants ( such as turfs and other ground covers), but no special data needs to be stored about these plansts.

Explanation / Answer

I would use 3 tables.

The first table would have a master list of each plant

plantId common latin wholesale retail type(tree, shrub, turf, etc)

 

Next I would have a different table for the trees:

plantId height caliper

 

Same for the Shrubs:

plantId size distance flowering(yes/no)

 

Not sure if this is what you're looking for or not. I don't see where 4 tables were coming from unless you were thinking of using turf as one and other ground covers as another. Since trees and shrubs are the only 2 that have special information about them, those are the only ones you need a separate table for. Turf and ground covers have no special information beyond what's listed in the first table.

 

The first table would be the main part of the crows foot and the trees and shrubs would each be a branch from the main list. I don't see where a 3rd branch is even needed.

 

I hope this helps.

Related Questions

Navigate

• Browse (All)
• Browse 1
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.