Table design, +260 columns

gvanaco

Hello,

Is it possible to make a table with more than 260 columns?

If not, underneath is what I would like to create

The title of every column exists out of 2 factors. One from 1 to 10 and the other from A to Z.

The titlename for a column is for example: 1A, 2A, 3A, ... 5G, 6G, 7G, ...8Z, 9Z, 10Z.

In the row I put a number. I know that I gonna have minimum 2500 rows.

The table may split up in other tables, but It have to stay user-fiendly.

At the end I gonna have to search the amount of 5G, 8Z in the table.
And other search is, give me all the rows that have more than 100 on a row.

Thanks for the help

leatherback

Hi,

Don't know if you COULD, but I know you SHOULD NOT set it up like this. Both from a programming perspective, as well as a query perspective.

Setup as table with a colum for label, and the rest of the info you want to store:

ID | label | answer
 1       1a      Yes
  2       5g     No
  3       2c      perhaps

etc

gvanaco

An visual example of what I would do but to many columns

rowID | 1A | 2A | 3A | 4A | ... | 8Z | 9Z | 10Z
  1     40    15    0     0         7    56   4
  2      7     30    4     9         0    0    0
  3      0     0      0     0        12   36   4
  4      0     1      7     8         6    4    0
...
2500   8     4      7     0         6    1     2

leatherback

I know what you described. And as I said: I would not do it this way.,
What is the logic of your way of designing the table this way? Why do you want to create this many colums?

leatherback

After your PM, I still maintain the opinion that you need a differently layed out structure.

You have two ratings:
$moeilijkheid (1- 10)
$Gevaarlijkheid (a-z)

So in your database you have:

table massief, stores info on each massief
massief_id | Massief_decription

table: Routes, stores all info on the routes
route_id | Massief_id | Description

table route_ratings: Store the ratings for each route
RRating_id | Route_nr | Moeilijkheid | gevaarlijkheid

You could add a table:
ratings, holds background information on each rating type
Rating_id | Description

I know this looks like a lot of information to store, and a lot of tables to create. But when you are going to do statictics, this is much easier to handle then the layout yu were suggesting. Do not worry about having a few thousand records. I have tables which hold 2million+ records which process requests very quickly.

gvanaco

I gonne give it a try.

Already thanks for a solution that ives me an other look.

gvanaco

leatherback

OK,

You will have to have a look at join syntax as well (At www.mysql.org)