NAME
Data::Type::Collection::DB - types from databases
SYNOPSIS
valid
' '
x 20, DB::VARCHAR( 20 );
valid
'2001-01-01'
, DB::DATE(
'MYSQL'
);
valid
'16 Nov 94 22:28:20 PST'
, DB::DATE(
'DATEPARSE'
);
valid
'9999-12-31 23:59:59'
, DB::DATETIME;
valid
'1970-01-01 00:00:00'
, DB::TIMESTAMP;
valid
'-838:59:59'
, DB::TIME;
valid
'2155'
, DB::YEAR;
valid
'69'
, DB::YEAR(2);
valid
'0'
x 20, DB::TINYTEXT;
valid
'0'
x 20, DB::MEDIUMTEXT;
valid
'0'
x 20, DB::LONGTEXT;
valid
'0'
x 20, DB::TEXT;
DESCRIPTION
Common types from databases. All vendor-specific types should have a special prefix. Example:
DB::TIME
DB::MYSQL::TIME
DB::ORA::TIME
TYPES
DB::DATE (since 0.01.01)
flexible date
Usage
DATE() emulates MYSQL builtin datatype
Depends
DB::DATETIME (since 0.01.25)
date and time combination
DB::ENUM (since 0.01.25)
Mysql
DB::LONGTEXT (since 0.01.25)
long text
DB::MEDIUMTEXT (since 0.01.25)
medium text
DB::SET (since 0.01.25)
set of strings
DB::TEXT (since 0.01.25)
"BLOB" sized dataset
DB::TIME (since 0.01.25)
time
Usage
[RANGE] ('-838:59:59' to '838:59:59')
DB::TIMESTAMP (since 0.01.25)
timestamp
Usage
[RANGE] ('1970-01-01 00:00:00' to sometime in the year 2037)
DB::TINYTEXT (since 0.01.25)
tiny text
DB::VARCHAR (since 0.01.25)
string with a limited length
DB::YEAR (since 0.01.25)
year
Usage
The allowable values are 1901 to 2155, 0000 in the 4-digit year format, and 1970-2069 if you use the 2-digit format (70-69) (default is 4-digit)
INTERFACE
CONTACT
Sourceforge http://sf.net/projects/datatype is hosting a project dedicated to this module. And I enjoy receiving your comments/suggestion/reports also via http://rt.cpan.org or http://testers.cpan.org.
AUTHOR
Murat Uenalan, <muenalan@cpan.org>