grep and I don't seem to be on the same page. Blame me for that,
I am the one who made the unusual statements.

imagine a world where 'Cop Killer' was removed from the CD.

I can imagine that, it wrecks your argument because we were
talking about fixed size arrays.

That your data structures need to support the requirements of
your business rules is true. But that is not an argument against
embedding arrays in a record, it would depend on the business rules.

I haven't recommended putting a fixed size array into a field.
I have suggested putting it into a set of fields. As an example:

create table acct_year (    -- G/L balances for a year
   gl_acct   varchar,
   year      int,
   bal_0     numeric(12,4), -- ending balances for qtrs
   bal_1     numeric(12,4),
   bal_2     numeric(12,4),
   bal_3     numeric(12,4)
);
[download]

On the Perl side I have found an array to be the best representation
of this info. Best so far, I'm still ready to refactor everything.

my $acct_year = { 
        gl_acct => '100',
        year => 2000,
        bal => [ 9100.03, 783.87, 6339.26, 12.06 ],
};
[download]