beezer that site you sent me has all car data when you view source, you could rip it from there if you want i'll try do it for ya.

 

ideally you want two tables one something like manid and manufacturer and another table with modelid,manid,model

So for example in your manufacturer table you'd have a record for each manufacturer

manid - 7
manufacturer - Ford

and in your model table a record for each model

modelid - 14
manid - 7
model - Mustang

modelid - 15
manid - 7
model - GT90

this is the best way to organise the data with the future in mind.


 

I was thinking of going with more than 2 tables though.
I'd have a table for all the manufacturers.

And then each manufacturer would have its own table.

Table (Manufacturer)
manid - 1
name - Ford

manid - 2
name - BMW

Then I'd have 2 extra tables.

Table (Ford)
manid - 1
modelid - 1
model - Munstang
manid - 1
modelid - 2
model - F150
Table (BMW)
manid - 2
modelid - 1
model - 316
manid - 2
modelid - 2
model - 320

What do you think? I think it would bring search results faster, less cpu, and backing up will be several smaller files. Not one big clump.

I'm also gonna have to look up how to make a database of images. Should be easy, usually I import the image right into the database so the client backup is easier. But this will have way too many images to put them in with the database, so a generic folder might possibly be the best way, renaming the file on upload to modelidmanid.jpg or whatever. What do you think?

-------------
Is Beezer gonna have to choke Google Adsense?

As for the images, a good `best of both worlds` solution could be:

1. Store the images in the database (blob)

2. Image gets requested, you fetch it from the database and write it to disk

3. Future requests for that image get served from disk