$dbh = DBI->connect(qq{DBI:CSV:csv_sep_char=\\|}, {RaiseError => 1} );

    # here goes the $sth->prepare ....

    $sth->execute();
    while (my @result = $sth->fetchrow_array()) {
        print $result[0], ", " # first field
              $result[1], ", " # second field and so on
              "\n"
    }
    $sth->finish();
    $dbh->disconnect();
[download]

 _  _ _  _  
(_|| | |(_|><
 _|   

Thanks gmax for the advice. I do plan on putting this into a real database sometime soon. I thought that since it already was in a text file, I'd learn to DBI query it first as the transition to converting and querying a real database might be a bit too much to handle in one fell swoop.

I know I don't always put enough info in my questions. I try to be courteous and keep it short and simple.

thanks for the replies
peppiv
if time is money....is it safe to say it's five dollars past three hundred?

Putting this into a database should be trivial once you are ready to do so. bcp is your friend (use "|" as your field terminator and "\n" as your row terminator and you're golden)

Are you getting an error with this code? If so we can help you more if you post it.

Just looking through it: you seem to be headed in the right direction. The only thing that i see is that you need single quotes around your "Yes" in your query so it reads:

Actually an even better way to do it is to use place holders, like this:

Then in your execute statement:

The use of place holders is really helpful because it escapes characters that can potentionally cause your query to fail. Not as important with this example since you have a hard-coded string but it is very important when you start using variables.

To get your data out you need to fetch it. I typically fetch data into array of hash references like this:

#execute statement here
my @data = (); # define an array
while(my $row = $sth->fetchrow_hashref()) {
     push(@data,$row);
}

# finish and disconnect
[download]

Then its a pretty simple matter to access all your data. Each hash key is the name of the field. So if you wanted the first field of the first entry in your data base you just dereference the hash like so:

my $field_1 = $data[0]->{'field_1'};
[download]

Of course if you want to process the data all at once you don't really need an array at all:

Hope that helps
Chris

 use strict;
    use DBI;
    use CGI::Carp qw(fatalsToBrowser);
    use CGI qw (:standard);
    print "Content-type: text/html\n\n";
    
     my $dbh = DBI->connect(qq{DBI:CSV:f_dir=/usr/local/etc/httpd/cgi-
+bin/}, {RaiseError => 1} );

     $dbh->{'sep_char' => "|", 'col_names' => ["timestamp", "email", "
+name", "address", "city", "state", "zip"]};
     my $sth = $dbh->prepare( q{SELECT * FROM export_list WHERE state 
+= ? });

     my $rc = $sth->execute ('OH');

     print "Query will return $sth->{NUM_OF_FIELDS} fields.\n\n";

     while (my @result = $sth->fetchrow_array()) {
        print "@result\n";
        }
     
     die $sth->errstr if $sth->err;

     $dbh->disconnect;
[download]


I've used the col_names attribute and I don't receive any errors for that line. However I do get this error:
Attempt to fetch row from a Non-SELECT statement at /usr/local/etc/httpd/cgi-bin/DBI_start3.pl line 23.(*the fetchrow_array statement line).I'm researching this now. Question - If an error statement comes up for line 23, is it safe to assume that the lines of code before that are executing OK? Assuming you're not jumping around with subs.

You are not specifying which table you are setting the column names on. Look at the DBD::CSV docs. Your columns should be set like so:

$dbh->{'csv_tables'}->{'export_list'}={
  'sep_char' => "|",
  'col_names' => [qw(timestamp email name address city state zip)]};
[download]

Also, execute returns no useful information on a select statement, so there is no point in saving its return value. On a non-select statement (e.g. update, delete), it returns the number of rows affected.

And your die() statement is useless since you have RaiseError set. If there is a DBI error, DBI will execute a die() on its own before you ever get to that die statement.