#!/usr/bin/perl # # DBD::CSV - A DBI driver for CSV and similar structured files # # This module is currently maintained by # # H.Merijn Brand # # See for full acknowledgements the last two pod sections in this file use strict; use warnings; require DynaLoader; require DBD::File; require IO::File; package DBD::CSV; use strict; use vars qw( @ISA $VERSION $ATTRIBUTION $drh $err $errstr $sqlstate ); @ISA = qw( DBD::File ); $VERSION = "0.49"; $ATTRIBUTION = "DBD::CSV $DBD::CSV::VERSION by H.Merijn Brand"; $err = 0; # holds error code for DBI::err $errstr = ""; # holds error string for DBI::errstr $sqlstate = ""; # holds error state for DBI::state $drh = undef; # holds driver handle once initialized sub CLONE # empty method: prevent warnings when threads are cloned { } # CLONE # --- DRIVER ------------------------------------------------------------------- package DBD::CSV::dr; use strict; use Text::CSV_XS (); use vars qw( @ISA @CSV_TYPES ); @CSV_TYPES = ( Text::CSV_XS::IV (), # SQL_TINYINT Text::CSV_XS::IV (), # SQL_BIGINT Text::CSV_XS::PV (), # SQL_LONGVARBINARY Text::CSV_XS::PV (), # SQL_VARBINARY Text::CSV_XS::PV (), # SQL_BINARY Text::CSV_XS::PV (), # SQL_LONGVARCHAR Text::CSV_XS::PV (), # SQL_ALL_TYPES Text::CSV_XS::PV (), # SQL_CHAR Text::CSV_XS::NV (), # SQL_NUMERIC Text::CSV_XS::NV (), # SQL_DECIMAL Text::CSV_XS::IV (), # SQL_INTEGER Text::CSV_XS::IV (), # SQL_SMALLINT Text::CSV_XS::NV (), # SQL_FLOAT Text::CSV_XS::NV (), # SQL_REAL Text::CSV_XS::NV (), # SQL_DOUBLE ); our @ISA = qw( DBD::File::dr ); our $imp_data_size = 0; our $data_sources_attr = undef; sub connect { my ($drh, $dbname, $user, $auth, $attr) = @_; my $dbh = $drh->DBD::File::dr::connect ($dbname, $user, $auth, $attr); $dbh and $dbh->{Active} = 1; $dbh; } # connect # --- DATABASE ----------------------------------------------------------------- package DBD::CSV::db; use strict; our $imp_data_size = 0; our @ISA = qw( DBD::File::db ); sub set_versions { my $this = shift; $this->{csv_version} = $DBD::CSV::VERSION; return $this->SUPER::set_versions (); } # set_versions my %csv_xs_attr; sub init_valid_attributes { my $dbh = shift; # Straight from Text::CSV_XS.pm my @xs_attr = qw( eol sep_char quote_char escape_char binary decode_utf8 auto_diag diag_verbose blank_is_undef empty_is_undef allow_whitespace allow_loose_quotes allow_loose_escapes allow_unquoted_escape always_quote quote_empty quote_space escape_null quote_binary keep_meta_info verbatim types callbacks ); @csv_xs_attr{@xs_attr} = (); $dbh->{csv_xs_valid_attrs} = [ @xs_attr ]; $dbh->{csv_valid_attrs} = { map {("csv_$_" => 1 )} @xs_attr, qw( class tables in csv_in out csv_out skip_first_row null sep quote escape )}; $dbh->{csv_readonly_attrs} = { }; $dbh->{csv_meta} = "csv_tables"; return $dbh->SUPER::init_valid_attributes (); } # init_valid_attributes sub get_csv_versions { my ($dbh, $table) = @_; $table ||= ""; my $class = $dbh->{ImplementorClass}; $class =~ s/::db$/::Table/; my $meta; $table and (undef, $meta) = $class->get_table_meta ($dbh, $table, 1); unless ($meta) { $meta = {}; $class->bootstrap_table_meta ($dbh, $meta, $table); } my $dvsn = eval { $meta->{csv_class}->VERSION (); }; my $dtype = $meta->{csv_class}; $dvsn and $dtype .= " ($dvsn)"; return sprintf "%s using %s", $dbh->{csv_version}, $dtype; } # get_csv_versions sub get_info { my ($dbh, $info_type) = @_; require DBD::CSV::GetInfo; my $v = $DBD::CSV::GetInfo::info{int ($info_type)}; ref $v eq "CODE" and $v = $v->($dbh); return $v; } # get_info sub type_info_all { my $dbh = shift; require DBD::CSV::TypeInfo; return [@$DBD::CSV::TypeInfo::type_info_all]; } # type_info_all # --- STATEMENT ---------------------------------------------------------------- package DBD::CSV::st; use strict; our $imp_data_size = 0; our @ISA = qw(DBD::File::st); package DBD::CSV::Statement; use strict; use Carp; our @ISA = qw(DBD::File::Statement); package DBD::CSV::Table; use strict; use Carp; our @ISA = qw(DBD::File::Table); sub bootstrap_table_meta { my ($self, $dbh, $meta, $table) = @_; $meta->{csv_class} ||= $dbh->{csv_class} || "Text::CSV_XS"; $meta->{csv_eol} ||= $dbh->{csv_eol} || "\r\n"; exists $meta->{csv_skip_first_row} or $meta->{csv_skip_first_row} = $dbh->{csv_skip_first_row}; $self->SUPER::bootstrap_table_meta ($dbh, $meta, $table); } # bootstrap_table_meta sub init_table_meta { my ($self, $dbh, $meta, $table) = @_; $self->SUPER::init_table_meta ($dbh, $table, $meta); my $csv_in = $meta->{csv_in} || $dbh->{csv_csv_in}; unless ($csv_in) { my %opts = ( binary => 1, auto_diag => 1 ); # Allow specific Text::CSV_XS options foreach my $attr (@{$dbh->{csv_xs_valid_attrs}}) { $attr eq "eol" and next; # Handles below exists $dbh->{"csv_$attr"} and $opts{$attr} = $dbh->{"csv_$attr"}; } $dbh->{csv_null} || $meta->{csv_null} and $opts{Text::CSV_XS->version < 1.18 ? "always_quote" : "quote_empty"} = $opts{blank_is_undef} = 1; my $class = $meta->{csv_class}; my $eol = $meta->{csv_eol}; $eol =~ m/^\A(?:[\r\n]|\r\n)\Z/ or $opts{eol} = $eol; for ([ "sep", ',' ], [ "quote", '"' ], [ "escape", '"' ], ) { my ($attr, $def) = ($_->[0]."_char", $_->[1]); $opts{$attr} = exists $meta->{$attr} ? $meta->{$attr} : exists $dbh->{"csv_$attr"} ? $dbh->{"csv_$attr"} : $def; } $meta->{csv_in} = $class->new (\%opts) or $class->error_diag; $opts{eol} = $eol; $meta->{csv_out} = $class->new (\%opts) or $class->error_diag; } } # init_table_meta my %compat_map = map { $_ => "csv_$_" } qw( class eof eol quote_char sep_char escape_char ); __PACKAGE__->register_compat_map (\%compat_map); sub table_meta_attr_changed { my ($class, $meta, $attr, $value) = @_; (my $csv_attr = $attr) =~ s/^csv_//; if (exists $csv_xs_attr{$csv_attr}) { for ("csv_in", "csv_out") { exists $meta->{$_} && exists $meta->{$_}{$csv_attr} and $meta->{$_}{$csv_attr} = $value; } } $class->SUPER::table_meta_attr_changed ($meta, $attr, $value); } # table_meta_attr_changed sub open_data { my ($self, $meta, $attrs, $flags) = @_; $self->SUPER::open_file ($meta, $attrs, $flags); if ($meta && $meta->{fh}) { $attrs->{csv_csv_in} = $meta->{csv_in}; $attrs->{csv_csv_out} = $meta->{csv_out}; if (my $types = $meta->{types}) { # XXX $meta->{types} is nowhere assigned and should better $meta->{csv_types} # The 'types' array contains DBI types, but we need types # suitable for Text::CSV_XS. my $t = []; for (@{$types}) { $_ = $_ ? $DBD::CSV::dr::CSV_TYPES[$_ + 6] || Text::CSV_XS::PV () : Text::CSV_XS::PV (); push @$t, $_; } $meta->{types} = $t; } if (!$flags->{createMode}) { my $array; my $skipRows = defined $meta->{skip_rows} ? $meta->{skip_rows} : defined $meta->{csv_skip_first_row} ? 1 : exists $meta->{col_names} ? 0 : 1; defined $meta->{skip_rows} or $meta->{skip_rows} = $skipRows; if ($skipRows--) { $array = $attrs->{csv_csv_in}->getline ($meta->{fh}) or croak "Missing first row due to ".$attrs->{csv_csv_in}->error_diag; unless ($meta->{raw_header}) { s/\W/_/g for @$array; } defined $meta->{col_names} or $meta->{col_names} = $array; while ($skipRows--) { $attrs->{csv_csv_in}->getline ($meta->{fh}); } } # lockMode is set 1 for DELETE, INSERT or UPDATE # no other case need seeking $flags->{lockMode} and # $meta->{fh}->can ("tell") and $meta->{first_row_pos} = $meta->{fh}->tell (); exists $meta->{col_names} and $array = $meta->{col_names}; if (!$meta->{col_names} || !@{$meta->{col_names}}) { # No column names given; fetch first row and create default # names. my $ar = $meta->{cached_row} = $attrs->{csv_csv_in}->getline ($meta->{fh}); $array = $meta->{col_names}; push @$array, map { "col$_" } 0 .. $#$ar; } } } } # open_file no warnings 'once'; $DBI::VERSION < 1.623 and *open_file = \&open_data; use warnings; sub _csv_diag { my @diag = $_[0]->error_diag; for (2, 3) { defined $diag[$_] or $diag[$_] = "?"; } return @diag; } # _csv_diag sub fetch_row { my ($self, $data) = @_; exists $self->{cached_row} and return $self->{row} = delete $self->{cached_row}; my $tbl = $self->{meta}; my $csv = $self->{csv_csv_in} or return do { $data->set_err ($DBI::stderr, "Fetch from undefined handle"); undef }; my $fields; eval { $fields = $csv->getline ($tbl->{fh}) }; unless ($fields) { $csv->eof and return; my @diag = _csv_diag ($csv); $diag[0] == 2012 and return; # Also EOF (broken in Text::CSV_XS-1.10) my $file = $tbl->{f_fqfn}; croak "Error $diag[0] while reading file $file: $diag[1] \@ line $diag[3] pos $diag[2]"; } @$fields < @{$tbl->{col_names}} and push @$fields, (undef) x (@{$tbl->{col_names}} - @$fields); $self->{row} = (@$fields ? $fields : undef); } # fetch_row sub push_row { my ($self, $data, $fields) = @_; my $tbl = $self->{meta}; my $csv = $self->{csv_csv_out}; my $fh = $tbl->{fh}; unless ($csv->print ($fh, $fields)) { my @diag = _csv_diag ($csv); my $file = $tbl->{f_fqfn}; return do { $data->set_err ($DBI::stderr, "Error $diag[0] while writing file $file: $diag[1] \@ line $diag[3] pos $diag[2]"); undef }; } 1; } # push_row no warnings 'once'; *push_names = \&push_row; use warnings; 1; __END__ =head1 NAME DBD::CSV - DBI driver for CSV files =head1 SYNOPSIS use DBI; # See "Creating database handle" below $dbh = DBI->connect ("dbi:CSV:", undef, undef, { f_ext => ".csv/r", RaiseError => 1, }) or die "Cannot connect: $DBI::errstr"; # Simple statements $dbh->do ("CREATE TABLE foo (id INTEGER, name CHAR (10))"); # Selecting my $sth = $dbh->prepare ("select * from foo"); $sth->execute; $sth->bind_columns (\my ($id, $name)); while ($sth->fetch) { print "id: $id, name: $name\n"; } # Updates my $sth = $dbh->prepare ("UPDATE foo SET name = ? WHERE id = ?"); $sth->execute ("DBI rocks!", 1); $sth->finish; $dbh->disconnect; =head1 DESCRIPTION The DBD::CSV module is yet another driver for the DBI (Database independent interface for Perl). This one is based on the SQL "engine" SQL::Statement and the abstract DBI driver DBD::File and implements access to so-called CSV files (Comma Separated Values). Such files are often used for exporting MS Access and MS Excel data. See L for details on DBI, L for details on SQL::Statement and L for details on the base class DBD::File. =head2 Prerequisites The only system dependent feature that DBD::File uses, is the C function. Thus the module should run (in theory) on any system with a working C, in particular on all Unix machines and on Windows NT. Under Windows 95 and MacOS the use of C is disabled, thus the module should still be usable. Unlike other DBI drivers, you don't need an external SQL engine or a running server. All you need are the following Perl modules, available from any CPAN mirror, for example http://search.cpan.org/ =over 4 =item DBI X A recent version of the L (Database independent interface for Perl). See below why. =item DBD::File X This is the base class for DBD::CSV, and it is part of the DBI distribution. As DBD::CSV requires a matching version of L which is (partly) developed by the same team that maintains DBD::CSV. See META.json or Makefile.PL for the minimum versions. =item SQL::Statement X A simple SQL engine. This module defines all of the SQL syntax for DBD::CSV, new SQL support is added with each release so you should look for updates to SQL::Statement regularly. It is possible to run C without this module if you define the environment variable C<$DBI_SQL_NANO> to 1. This will reduce the SQL support a lot though. See L for more details. Note that the test suite does only test in this mode in the development environment. =item Text::CSV_XS X This module is used to read and write rows in a CSV file. =back =head2 Installation Installing this module (and the prerequisites from above) is quite simple. The simplest way is to install the bundle: $ cpan Bundle::CSV Alternatively, you can name them all $ cpan Text::CSV_XS DBI DBD::CSV or even trust C to resolve all dependencies for you: $ cpan DBD::CSV If you cannot, for whatever reason, use cpan, fetch all modules from CPAN, and build with a sequence like: gzip -d < DBD-CSV-0.40.tgz | tar xf - (this is for Unix users, Windows users would prefer WinZip or something similar) and then enter the following: cd DBD-CSV-0.40 perl Makefile.PL make test If any tests fail, let us know. Otherwise go on with make install UNINST=1 Note that you almost definitely need root or administrator permissions. If you don't have them, read the ExtUtils::MakeMaker man page for details on installing in your own directories. L. =head2 Supported SQL Syntax All SQL processing for DBD::CSV is done by SQL::Statement. See L for more specific information about its feature set. Features include joins, aliases, built-in and user-defined functions, and more. See L for a description of the SQL syntax supported in DBD::CSV. Table- and column-names are case insensitive unless quoted. Column names will be sanitized unless L is true. =head1 Using DBD::CSV with DBI For most things, DBD-CSV operates the same as any DBI driver. See L for detailed usage. =head2 Creating a database handle (connect) Creating a database handle usually implies connecting to a database server. Thus this command reads use DBI; my $dbh = DBI->connect ("dbi:CSV:", "", "", { f_dir => "/home/user/folder", }); The directory tells the driver where it should create or open tables (a.k.a. files). It defaults to the current directory, so the following are equivalent: $dbh = DBI->connect ("dbi:CSV:"); $dbh = DBI->connect ("dbi:CSV:", undef, undef, { f_dir => "." }); $dbh = DBI->connect ("dbi:CSV:f_dir=."); We were told, that VMS might - for whatever reason - require: $dbh = DBI->connect ("dbi:CSV:f_dir="); The preferred way of passing the arguments is by driver attributes: # specify most possible flags via driver flags $dbh = DBI->connect ("dbi:CSV:", undef, undef, { f_schema => undef, f_dir => "data", f_dir_search => [], f_ext => ".csv/r", f_lock => 2, f_encoding => "utf8", csv_eol => "\r\n", csv_sep_char => ",", csv_quote_char => '"', csv_escape_char => '"', csv_class => "Text::CSV_XS", csv_null => 1, csv_tables => { info => { f_file => "info.csv" } }, RaiseError => 1, PrintError => 1, FetchHashKeyName => "NAME_lc", }) or die $DBI::errstr; but you may set these attributes in the DSN as well, separated by semicolons. Pay attention to the semi-colon for C (as seen in many CSV exports from MS Excel) is being escaped in below example, as is would otherwise be seen as attribute separator: $dbh = DBI->connect ( "dbi:CSV:f_dir=$ENV{HOME}/csvdb;f_ext=.csv;f_lock=2;" . "f_encoding=utf8;csv_eol=\n;csv_sep_char=\\;;" . "csv_quote_char=\";csv_escape_char=\\;csv_class=Text::CSV_XS;" . "csv_null=1") or die $DBI::errstr; Using attributes in the DSN is easier to use when the DSN is derived from an outside source (environment variable, database entry, or configure file), whereas specifying entries in the attribute hash is easier to read and to maintain. =head2 Creating and dropping tables You can create and drop tables with commands like the following: $dbh->do ("CREATE TABLE $table (id INTEGER, name CHAR (64))"); $dbh->do ("DROP TABLE $table"); Note that currently only the column names will be stored and no other data. Thus all other information including column type (INTEGER or CHAR (x), for example), column attributes (NOT NULL, PRIMARY KEY, ...) will silently be discarded. This may change in a later release. A drop just removes the file without any warning. See L for more details. Table names cannot be arbitrary, due to restrictions of the SQL syntax. I recommend that table names are valid SQL identifiers: The first character is alphabetic, followed by an arbitrary number of alphanumeric characters. If you want to use other files, the file names must start with "/", "./" or "../" and they must not contain white space. =head2 Inserting, fetching and modifying data The following examples insert some data in a table and fetch it back: First, an example where the column data is concatenated in the SQL string: $dbh->do ("INSERT INTO $table VALUES (1, ". $dbh->quote ("foobar") . ")"); Note the use of the quote method for escaping the word "foobar". Any string must be escaped, even if it does not contain binary data. Next, an example using parameters: $dbh->do ("INSERT INTO $table VALUES (?, ?)", undef, 2, "It's a string!"); Note that you don't need to quote column data passed as parameters. This version is particularly well designed for loops. Whenever performance is an issue, I recommend using this method. You might wonder about the C. Don't wonder, just take it as it is. :-) It's an attribute argument that I have never used and will be passed to the prepare method as the second argument. To retrieve data, you can use the following: my $query = "SELECT * FROM $table WHERE id > 1 ORDER BY id"; my $sth = $dbh->prepare ($query); $sth->execute (); while (my $row = $sth->fetchrow_hashref) { print "Found result row: id = ", $row->{id}, ", name = ", $row->{name}; } $sth->finish (); Again, column binding works: The same example again. my $sth = $dbh->prepare (qq; SELECT * FROM $table WHERE id > 1 ORDER BY id; ;); $sth->execute; my ($id, $name); $sth->bind_columns (undef, \$id, \$name); while ($sth->fetch) { print "Found result row: id = $id, name = $name\n"; } $sth->finish; Of course you can even use input parameters. Here's the same example for the third time: my $sth = $dbh->prepare ("SELECT * FROM $table WHERE id = ?"); $sth->bind_columns (undef, \$id, \$name); for (my $i = 1; $i <= 2; $i++) { $sth->execute ($id); if ($sth->fetch) { print "Found result row: id = $id, name = $name\n"; } $sth->finish; } See L for details on these methods. See L for details on the WHERE clause. Data rows are modified with the UPDATE statement: $dbh->do ("UPDATE $table SET id = 3 WHERE id = 1"); Likewise you use the DELETE statement for removing rows: $dbh->do ("DELETE FROM $table WHERE id > 1"); =head2 Error handling In the above examples we have never cared about return codes. Of course, this is not recommended. Instead we should have written (for example): my $sth = $dbh->prepare ("SELECT * FROM $table WHERE id = ?") or die "prepare: " . $dbh->errstr (); $sth->bind_columns (undef, \$id, \$name) or die "bind_columns: " . $dbh->errstr (); for (my $i = 1; $i <= 2; $i++) { $sth->execute ($id) or die "execute: " . $dbh->errstr (); $sth->fetch and print "Found result row: id = $id, name = $name\n"; } $sth->finish ($id) or die "finish: " . $dbh->errstr (); Obviously this is tedious. Fortunately we have DBI's I attribute: $dbh->{RaiseError} = 1; $@ = ""; eval { my $sth = $dbh->prepare ("SELECT * FROM $table WHERE id = ?"); $sth->bind_columns (undef, \$id, \$name); for (my $i = 1; $i <= 2; $i++) { $sth->execute ($id); $sth->fetch and print "Found result row: id = $id, name = $name\n"; } $sth->finish ($id); }; $@ and die "SQL database error: $@"; This is not only shorter, it even works when using DBI methods within subroutines. =head1 DBI database handle attributes =head2 Metadata The following attributes are handled by DBI itself and not by DBD::File, thus they all work as expected: Active ActiveKids CachedKids CompatMode (Not used) InactiveDestroy Kids PrintError RaiseError Warn (Not used) The following DBI attributes are handled by DBD::File: =over 4 =item AutoCommit X Always on =item ChopBlanks X Works =item NUM_OF_FIELDS X Valid after C<$sth-Eexecute> =item NUM_OF_PARAMS X Valid after C<$sth-Eprepare> =item NAME X =item NAME_lc X =item NAME_uc X Valid after C<$sth-Eexecute>; undef for Non-Select statements. =item NULLABLE X Not really working. Always returns an array ref of one's, as DBD::CSV does not verify input data. Valid after C<$sth-Eexecute>; undef for non-Select statements. =back These attributes and methods are not supported: bind_param_inout CursorName LongReadLen LongTruncOk =head1 DBD-CSV specific database handle attributes In addition to the DBI attributes, you can use the following dbh attributes: =head2 DBD::File attributes =over 4 =item f_dir X This attribute is used for setting the directory where CSV files are opened. Usually you set it in the dbh and it defaults to the current directory ("."). However, it may be overridden in statement handles. =item f_dir_search X This attribute optionally defines a list of extra directories to search when opening existing tables. It should be an anonymous list or an array reference listing all folders where tables could be found. my $dbh = DBI->connect ("dbi:CSV:", "", "", { f_dir => "data", f_dir_search => [ "ref/data", "ref/old" ], f_ext => ".csv/r", }) or die $DBI::errstr; =item f_ext X This attribute is used for setting the file extension. =item f_schema X This attribute allows you to set the database schema name. The default is to use the owner of C. C is allowed, but not in the DSN part. my $dbh = DBI->connect ("dbi:CSV:", "", "", { f_schema => undef, f_dir => "data", f_ext => ".csv/r", }) or die $DBI::errstr; =item f_encoding X This attribute allows you to set the encoding of the data. With CSV, it is not possible to set (and remember) the encoding on a column basis, but DBD::File now allows the encoding to be set on the underlying file. If this attribute is not set, or undef is passed, the file will be seen as binary. =item f_lock X With this attribute you can specify a locking mode to be used (if locking is supported at all) for opening tables. By default, tables are opened with a shared lock for reading, and with an exclusive lock for writing. The supported modes are: =over 2 =item 0 X<0> Force no locking at all. =item 1 X<1> Only shared locks will be used. =item 2 X<2> Only exclusive locks will be used. =back =back But see L. =head2 DBD::CSV specific attributes =over 4 =item csv_class The attribute I controls the CSV parsing engine. This defaults to C, but C can be used in some cases, too. Please be aware that C does not care about any edge case as C does and that C is probably about 100 times slower than C. =back =head2 Text::CSV_XS specific attributes =over 4 =item csv_eol X =item csv_sep_char X =item csv_quote_char X =item csv_escape_char X =item csv_csv X The attributes I, I, I and I are corresponding to the respective attributes of the I (usually Text::CSV_CS) object. You may want to set these attributes if you have unusual CSV files like F or MS Excel generated CSV files with a semicolon as separator. Defaults are C<\015\012>", C<,>, C<"> and C<">, respectively. The I attribute defines the end-of-line pattern, which is better known as a record separator pattern since it separates records. The default is windows-style end-of-lines C<\015\012> for output (writing) and unset for input (reading), so if on unix you may want to set this to newline (C<\n>) like this: $dbh->{csv_eol} = "\n"; It is also possible to use multi-character patterns as record separators. For example this file uses newlines as field separators (sep_char) and the pattern "\n__ENDREC__\n" as the record separators (eol): name city __ENDREC__ joe seattle __ENDREC__ sue portland __ENDREC__ To handle this file, you'd do this: $dbh->{eol} = "\n__ENDREC__\n" , $dbh->{sep_char} = "\n" The attributes are used to create an instance of the class I, by default Text::CSV_XS. Alternatively you may pass an instance as I, the latter takes precedence. Note that the I attribute I be set to a true value in that case. Additionally you may overwrite these attributes on a per-table base in the I attribute. =item csv_null X With this option set, all new statement handles will set C and C in the CSV parser and writer, so it knows how to distinguish between the empty string and C or C. You cannot reset it with a false value. You can pass it to connect, or set it later: $dbh = DBI->connect ("dbi:CSV:", "", "", { csv_null => 1 }); $dbh->{csv_null} = 1; =item csv_tables X This hash ref is used for storing table dependent metadata. For any table it contains an element with the table name as key and another hash ref with the following attributes: =item csv_* X All other attributes that start with C and are not described above will be passed to C (without the C prefix). These extra options are only likely to be useful for reading (select) handles. Examples: $dbh->{csv_allow_whitespace} = 1; $dbh->{csv_allow_loose_quotes} = 1; $dbh->{csv_allow_loose_escapes} = 1; See the C documentation for the full list and the documentation. =back =head2 Driver specific attributes =over 4 =item f_file X The name of the file used for the table; defaults to "$dbh->{f_dir}/$table" =item eol X =item sep_char X =item quote_char X =item escape_char X =item class X =item csv X These correspond to the attributes I, I, I, I, I and I. The difference is that they work on a per-table basis. =item col_names X =item skip_first_row X By default DBD::CSV assumes that column names are stored in the first row of the CSV file and sanitizes them (see C below). If this is not the case, you can supply an array ref of table names with the I attribute. In that case the attribute I will be set to FALSE. If you supply an empty array ref, the driver will read the first row for you, count the number of columns and create column names like C, C, ... Note that column names that match reserved SQL words will cause unwanted and sometimes confusing errors. If your CSV has headers that match reserved words, you will require these two attributes. If C looks like select,from 1,2 the select query would result in C