First you need to figure out how to parse those records out as records, and which type of record each one is. Then, a hash of hashes (HoH) of the records makes sense to organize them.
Something like the below makes sense to me as your data structure. Keying the outside hash to the common key for your tables allows you to add data to the anonymous hashes inside as you find new records for an employee, rather than having to put an employee record together completely before storing it in the data structure. Then, just walk over the outside hash and output the key and the data from inside the anonymous hash for each employee in turn.
@employee = (
'227' => {
'uid' => 'simpsonh',
'sn' => 'Simpson',
'givenname' => 'Homer',
'manager' => 'burnsm',
'telephoneNumber' => '2183445555',
'departmentNumber' => 38,
'title' => 'Nuclear Plant Operator',
'roomNumber' => 7,
'buildingName' => 'Nuclear Resources'
},
222 => {
# rest of entry info here
}
);
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.