Hello All,

I have some code (an old sci application) reading an ASCII table (sic!)
with something like (the line is the record)

Height\Temperature 10 20 30 ...
0 430 420 4
1000 400 340
2000
etc

As you can see the first line and column are really the "coordinates" (say
X,Y) while the values of
interest (Z) are in the matrix starting from element (2,2).
Now as you might guess, somebody had the idea to move the data inside a
relational DB
Supposing you don't know how many X and Y you might have, how many tables
would you
use and with what structure ?

I can't really think of a good and universal solution.
I don't like the idea of having a table with the X values, another one with
the Y and then
still another one with the Z values for these points. Also I would avoid
overdimensioning the tables.
Any suggestion/link most appreciated.

Thank you
- Gio