<moderators note> Please remember to write your response BELOW the previous text. --- In [email protected], "John Magee" <[EMAIL PROTECTED]> wrote: > > Create a table called invoice that has all the customer information and an invoice number...all the 'single piece' information > > Create a table called 'invoice items' or some such...create a foreign key that links to invoice but the uniquely id'd invoice number....put all the item information for whatever is being ordered here, qty, prices, sizes, etc.... > > Standard database design > > (and the first question i've ever been able to answer on this board) > > ----- Original Message ----- > From: Srihari > To: [email protected] > Sent: Friday, April 18, 2008 8:02 AM > Subject: [php-list] How to Design database for billing application > > > Hi to everybody, > > I am srihari from India. > I am developing a online billing application for a retail shop that > have many branches in country.A person in any shop can generate a bill > for the customer.The bill can be viewed and edited in future. > > The bill may contain any number(may be infinity) of items with its > unique rate and qty. > > > NOW I WANT TO KNOW HOW TO DESIGN DATABASE FOR STORING THE ITEMS OF THE > BILL IN DATABASE? > > If you have any idea kindly share with me... > > I am available at [EMAIL PROTECTED] And > [EMAIL PROTECTED] > > > > ------------------------------------
Thanks a lot john But if the number of invoice with many items increases then Db would become huge which make the retriving process into a slow process. Eg: 100 invoices with 20 items in each then the records would be 2000 right.This may increase the time of retriving data from DB
