Serializing even a large list into 1 column is not a bad thing necessairly.
The thing is when you update that column, you have to rewrite the whole
thing. If you expect lots of items and a frequent update it might be better
to store each item in a column as stack says above.
Another question you c
> one column with lots of data (i.e. one huge column in each row) does not
> seem the greatest idea to me.
>
> Any suggestions as to how I should approach this would be great. Many
> thanks.
> --
> View this message in context:
> http://www.nabble.com/Best-practice-design-que
ts of data (i.e. one huge column in each row) does not
seem the greatest idea to me.
Any suggestions as to how I should approach this would be great. Many
thanks.
--
View this message in context:
http://www.nabble.com/Best-practice-design-query-for-storing-a-list-array-of-values-tp25530827p25530827
