IDC资讯中心
based on the information in the previous section, we have a good understanding of what our database schema should look like. the following tables list our database structure:
tblauctions tblauctionitems
aid unique id to keep track of records autonumber iid unique id to keep track of records autonumber
startdate date the auction started date/time aid which auction does this item belong to? (foreign key to auctions table) integer
enddate date the auction is to end date/time name name of the item being sold text
sellerid the id of the seller. (foreign key to user table) integer description description of the item being sold text
minprice minimum price to sell (specified by the seller) money
tblauctionbids increment value to increment proxy bids by (specified by the seller) money
bid unique id to keep track of records autonumber available number of items available to sell integer
iid unique id to keep track of items (foreign key to auctionitem table) integer
uid unique id to keep track of bidders (foreign key to auctionusers table) integer tblauctionusers
winprice current price for a user (calculated by application) money uid unique id to keep track of records autonumber
maxbid maximum price for a user money name name of user text
biditems the number of items this user bid for integer
winitems the number of items this user would win if the auction ended immediately integer
time the last time this bid was updated date/time
note that the above tables are simply used for example. you may decide to store more information for your purposes (i.e., you may store more than just a name in the user table). already, however, the schema is getting kind of complex – each table has foreign keys to one or more other tables.
note: you can use a pre-existing user table if you wish. we simply provide the tblauctionusers table definition for completeness sake.
