StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17326095
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-26T16:55:21.613
FavoriteCount
0
LastActivityDate
2013-06-26T16:55:21.613
LastEditDate
LastEditorUserId
0
OwnerUserId
368630
ParentId
17305273
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Text::CSV will store your data as an array of hashes with each hash key being the column name. This seems to make the most sense. For example: <pre><code>my %employee = %{ $employee_array[2] }; #Row #3 of your file: print "The name of the third employee is $employee{first_name} $employee{last_name}\n"; </code></pre> Thus, a single row of your array contains all of the data for that employee. In your case, you'd have to keep the index the same across multiple arrays: <pre><code>print "The name of the third employee is $first_name[2] $last_name[2]\n"; </code></pre> If you had a function that operated on the employee, you'd have to pass all of your arrays to the function: <pre><code>print_paycheck($first_name[1], $last_name[1], $employee_num[1], $hire_date[1]...); </code></pre> While if you had an array of hashes, you could do this: <pre><code>print_paycheck($employee_array[1]); </code></pre> I take it that you don't know about references. Many beginner Perl books don't discuss them, and they're not an obvious extension of Perl. However, references allow you to make these more complex data structures. Fortunately, Perldoc has an excellent <a href="http://perldoc.perl.org/perlreftut.html" rel="nofollow">Tutorial</a>. I suggest that you read it. In reality, you probably want to to store your data keyed by the employee number, so you want a hash of hashes. Here's an example of a hash of hashes. NOTE: This is not the way I'd do the program. First, I would use <code>Text::CSV</code> if available, and then I would actually use an object oriented approach. However, I wanted to keep this as a simple hash of hashes: <pre><code>use warnings; use strict; use feature qw(say); use Data::Dumper; my %employee_hash; <DATA>; #Field Names while ( my $employee_data = <DATA> ) { chomp $employee_data; my ($employee, $birth_date, $first_name, $last_name, $gender, $hire_date) = split /,/, $employee_data; $employee_hash{$employee}->{birth_date} = $birth_date; $employee_hash{$employee}->{first_name} = $first_name; $employee_hash{$employee}->{last_name} = $last_name; $employee_hash{$employee}->{gender} = $gender; $employee_hash{$employee}->{hire_date} = $hire_date; } for my $employee ( sort keys %employee_hash ) { my $gender; if ( $employee_hash{$employee}->{gender} eq "M" ) { $gender = "he"; } else { $gender = "she"; } printf qq(Employee: %s is %s %s and %s was hired on %s\n), $employee, $employee_hash{$employee}->{first_name}, $employee_hash{$employee}->{last_name}, $gender, $employee_hash{$employee}->{hire_date}; } __DATA__ emp_no,birth_date,first_name,last_name,gender,hire_date 10001,1953-09-02,Georgi,Facello,M,1986-06-26 10002,1964-06-02,Bezalel,Simmel,F,1985-11-21 10003,1959-12-03,Parto,Bamford,M,1986-08-28 10004,1954-05-01,Chirstian,Koblick,M,1986-12-01 10005,1955-01-21,Kyoichi,Maliniak,M,1989-09-12 </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POconvert csv in perl hash of arrays
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDavid W.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.