Re: ... arrays in fields ...

[Matt Koch]

Hi there Ram,

thanks for the response. Yes, I had come across the SET command earlier, but it really seems to require ALTER queries to maintain. This in turn represents a table change, not just a field change. I tend to shy away from that. The user comments also brought the normalization issue to my attention, although I do not think it applies here.

I really wanted to store, say, all (not just one) pressures of a pump performance curve in one field, and all the associated (not just one) flows in another field. Each record could have a different pump performance, represented by these two fields.

But I guess the PostGreSQL simplicity of an array data type (as opposed to a simple float data type) for a field is not implemented in MySQL. Shame.

Thanks for your hints, though. Regards,

Matt