DBIx::DBSchema::Column - Column objects |
DBIx::DBSchema::Column - Column objects
use DBIx::DBSchema::Column;
#named params with a hashref (preferred) $column = new DBIx::DBSchema::Column ( { 'name' => 'column_name', 'type' => 'varchar' 'null' => 'NOT NULL', 'length' => 64, 'default' => '', 'local' => '', } );
#list $column = new DBIx::DBSchema::Column ( $name, $sql_type, $nullability, $length, $default, $local );
$name = $column->name; $column->name( 'name' );
$sql_type = $column->type; $column->type( 'sql_type' );
$null = $column->null; $column->null( 'NULL' ); $column->null( 'NOT NULL' ); $column->null( '' );
$length = $column->length; $column->length( '10' ); $column->length( '8,2' );
$default = $column->default; $column->default( 'Roo' );
$sql_line = $column->line; $sql_line = $column->line($datasrc);
$sql_add_column = $column->sql_add_column; $sql_add_column = $column->sql_add_column($datasrc);
DBIx::DBSchema::Column objects represent columns in tables (see the DBIx::DBSchema::Table manpage).
Note: If you pass a scalar reference as the default rather than a scalar value, it will be dereferenced and quoting will be forced off. This can be used to pass SQL functions such as $now()
or explicit empty strings as ''
as
defaults.
The data source can be specified by passing an open DBI database handle, or by passing the DBI data source name, username and password.
Although the username and password are optional, it is best to call this method with a database handle or data source including a valid username and password - a DBI connection will be opened and the quoting and type mapping will be more reliable.
If passed a DBI data source (or handle) such as `DBI:mysql:database' or `DBI:Pg:dbname=database', will use syntax specific to that database engine. Currently supported databases are MySQL and PostgreSQL. Non-standard syntax for other engines (if applicable) may also be supported in the future.
The data source can be specified by passing an open DBI database handle, or by passing the DBI data source name, username and password.
Although the username and password are optional, it is best to call this method with a database handle or data source including a valid username and password - a DBI connection will be opened and the quoting and type mapping will be more reliable.
If passed a DBI data source (or handle) such as `DBI:Pg:dbname=database', will use PostgreSQL-specific syntax. Non-standard syntax for other engines (if applicable) may also be supported in the future.
#Optionally, the data source can be specified by passing an open DBI database #handle, or by passing the DBI data source name, username and password. # #If passed a DBI data source (or handle) such as `DBI:Pg:dbname=database', will #use PostgreSQL-specific syntax. Non-standard syntax for other engines (if #applicable) may also be supported in the future. # #If not passed a data source (or handle), or if there is no driver for the #specified database, will attempt to use generic SQL syntax.
Or should, someday. Right now it knows how to change NOT NULL into NULL and vice-versa.
Ivan Kohler <ivan-dbix-dbschema@420.am>
Copyright (c) 2000-2006 Ivan Kohler Copyright (c) 2007 Freeside Internet Services, Inc. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
The new()
method should warn that
``Old-style $class creation without named parameters is deprecated!''
Better documentation is needed for sql_add_column
line()
and sql_add_column()
hav database-specific foo that should be abstracted
into the DBIx::DBSchema:DBD:: modules.
the DBIx::DBSchema::Table manpage, the DBIx::DBSchema manpage, the DBIx::DBSchema::DBD manpage, the DBI manpage
DBIx::DBSchema::Column - Column objects |