view release on metacpan or  search on metacpan

test_data/driver_characteristics  view on Meta::CPAN

    Details of the syntax of the dsn including any optional parts.

The DBI->connect Data Source Name (DSN) should include the directory
where the dbt files are located as the third part.

  dbi:XBase:/path/to/directory

It defaults to current directory.

    Details of any driver specific attributes applicable to the
    connect method.

There are no driver specific attributes for the DBI->connect method.

=head2 Numeric Data Handling

    What numeric data types do the database and driver support? (INTEGER,
    FLOAT, NUMBER(p,s) etc).  What is the maximum scale and precision for
    each type?

Generic NUMBER(p,s) and FLOAT(p,s), INTEGER(l). Maximul scale and
precision unknown, resp. limited by Perl's handling of numbers. In
the dbf files, the numbers are stored as ASCII strings, or binary
integers or floats.

Numbers are always returned converted to numbers, so numbers outside
of Perl's valid range are not possible (even if this restriction might
be withdrawn in the future).

    Does the database and driver support numbers outside the valid range
    for perl numbers?

No.

    Are numbers returned as strings in this case?

N/A

=head2 String Data Handling

    What string data types does the database support? (CHAR, VARCHAR, etc)

DBD::XBase knows CHAR(length) and VARCHAR(length), both are stored as
fixed length chars however. These can contain any binary values. No
charset options are recongnized.

    What is the maximum size for each type?

65535 characters (even if the older dBase's only allowed 255
characters, so created dbf might not be porteble to other xbase-like
software).

    Are any types blank padded? If so which, e.g., CHAR.

Yes.

    How does the database handle data with the 8th bit set (national
    language character sets etc)?

Data with the 8th bit set are handles transparently, no national
language character set conversions are done.

    Is Unicode supported?

No (there is no notion of charsets).

=head2 Date Data Handling

    What date, time and date+time data types are supported
    and what is their valid range and resolution?

Default (and only possible) date format for input and output is 8 char
string 'YYYYMMDD'. DBD::XBase doesn't check for validity of this
string.

The datetime type works internally with the precision up to 1/1000 s.
DBD::XBase currently supports this using Un*x standard
seconds-since-epoch value (possibly with decimal part). This might
change in the future.

    What date, time and date+time formats are supported?

No formats except the defaults are supported.

    What is the default output format for each?

'YYYYMMDD' and number of seconds since 1970/1/1.

    What is the default input format for each?
    Are multiple input format recognised?

'YYYYMMDD' and number of seconds since 1970/1/1. This is the only
possibility.

    If only part of a date is specified, how does the rest default?

No partial definitions are allowed.

    If two digit years can be used, how is the century determined?

N/A

    Can the default format be changed? If so, how (both for a single
    expression in an sql statement, and as a database connection default)?

No.

    How can I get the current date+time in an SQL expression?

There is no way to get the current date/time.

    How can I input date and date+time values in other formats?

N/A

    How can I output date and date+time values in other formats?

N/A

    What kinds of date and time arithmetic and functions are supported?