Maybe the char array link is wrong ? I don't think an array of arrays is good for my case. I'll probably go for json or separate table since it looks it's not possible to use composite-types.
Why do you think you need an array of theType v. a dependent table of theType. This tack is of course immune to to most future type changess.
Sent from my iPhone
Interesting. Of course any decent mapper will return "the whole row". And would it be less disk intensive as an array of "struct ( where struct is implemented as an array)". From other threads [1] [2] I've come to understand the datatype overhead per native type will be applied per type instance per array element.