At the very least, you would want to create the following tables with the fields included: Products (title, description, reservation price, photo, id); Users (name, password, email address, credit card type and number, shipping address); Bids (amount, item id, bidder email id). They don’t all have to be produced at once. For example, you might want to create an Items table, fill it with sample data, and then build a user interface to solve any problems that occur.
Populate the sample data tables. You can do this on your own prompt, but a simpler way to do this is to use a database wrapper such as PEAR DB (Database Functions Library) that gives you access to the basic functions you need to create, read, change, and remove. This feature will allow the administrator to add, change, and remove items as required.
The presentational aspects of the site will be handled by a view template, which will include HTML and CSS, which will specify, for example, the properties of each object (colour, font, size) as well as its location on the website. This template will be invoked as required by the controller.
Establish the logic of bidding. When users bid on an object, verify that it is authenticated and that their bid is higher than the last approved bid (or reserve, if there are no bids). If that is the case, store their bid in the bid table.