I jrealized that I cant do it this way, I will have to have a seperate table for each part. Becuase the way the xml is structured I cant put all the d part values into one set of columns and the n part values in a different... so I will have to have a third table for "part" info... hmmm..




>To clarify my question: How you you store this data in a table.
>
>Right now, Im tentative on having the following schema
>
>forecast
>---------------
>zip
>lastupdate
>
>
>forecastday
>---------------
>zip
>day#
>high
>low
>sunr
>suns
>dicon --This is specific to the "d" part of each day
>dt
>...
>nicon --this is for the "n" part of each day
>nt
>
>
>
>Any other ideas on how to store this data? I was thinking of having a "part" table that stores data for each part , but since (Im assuming) there is always 2 parts to a day, it could just be stored in the forecastday table.