While I am not one to insist on 3rd normal form or anything like that, I would recommend you look at normalizing this db a bit. Perhaps you could create a table or two for the companies and contact info, it can be dangerous to limit yourself to one phone number or even one address in many cases. Obviously there are tradeoffs between normalizing data and speed of queries, but I thnk the suggestion still holds. hth, -richard
On 6/19/08, joshuajonah <[EMAIL PROTECTED]> wrote: > > > I am making a database of advertisers, product categories, products > (advertiser+product category), retailers, and retailers stock > (retailer + products) > > Here is my diagram of the topology: > http://www.joshuajonah.com/database.png > > Here's my models.py: http://dpaste.com/57676/ > > Do you see any problems before i sync this? can you think of any > better way of structuring this? there will be a LOT of records. Thanx > guys. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
