Create a database ERD.

Design a database for the owners of a store called Antiques Pasadena. Antiques Pasadena buys and sells one-of-a-kind antiques of all kinds (examples: furniture, jewelry, china, clothing and paintings) An ItemNumber uniquely identifies each item, but no two items are alike in the store, so this is nota standard inventory application. In a standard inventory application, the database designer assumes that there will be more than one of a given item in inventory and keeps track of the quantity on hand of that item; in this application, the designer must assume that each ItemNumber represents a unique item and that the quantity on hand will be 1. The owners of Antiques Pasadena decide what composes an "item." For example, the owners may decide that a single spoon is an "item" or they might decide that an entire silver place setting is an "item." This decision is made when the item is purchased and made available for sale in the store, This decision does not change once it has been made. Each item is also characterized by a Description, AskingPrice, InitialCondition, and open-ended Comments about the item The owners of Antiques Pasadena work with many different individuals, called Clients, who sell items to and buy items from the store. Some clients only sell items to Antiques Pasadena, some only buy items from Antiques Pasadena and some both sell and buy. A client is identified by a ClientID and is also described by a ClientName and PhoneNumber. The owners aren't planning on keeping track of whether a client is a buyer or a seller in the actual Client data. When Antiques Pasadena sells an item in stock to a client, the owners want to record information about the sale such as the actual selling price, sales tax, date sold, and commission paid. When Antiques Pasadena buys an item from a client, the owners want to record the purchase cost, date purchased, and condition at the time of purchase