Agreed that a seperate relational table is the way to go. Supports first normal form.
But I would put all numbers on the same table and have an attribute marking primary contact number (or a ranking of contact numbers to be able to sort by importance) if desired.
This makes coding much...
I don't use the CSV in the DBD module but these should still apply.
You can get the column names of a statement using the statement attribute NAME, NAME_uc or NAME_lc. EX:
my $dbh = (... however you connect...);
my $stmt = qq(select * from table);
my $csrStmt = $dbh->prepare($stmt);
my @cols =...
A few thing I see may be potential problems.
I don't think you have anything in @newcode.
It looks like you take $code and send it to a file with FH CODE2 and then try reading it into @newcode with FH CODE. But the OPEN statement for CODE is for output not input which will make @newcode null...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.