sql::translator::parser::dbi(3pm) [debian man page]

SQL::Translator::Parser::DBI(3pm)			User Contributed Perl Documentation			 SQL::Translator::Parser::DBI(3pm)

NAME

       SQL::Translator::Parser::DBI - "parser" for DBI handles

SYNOPSIS

	 use DBI;
	 use SQL::Translator;

	 my $dbh = DBI->connect('dsn', 'user', 'pass',
	     {
		 RaiseError	  => 1,
		 FetchHashKeyName => 'NAME_lc',
	     }
	 );

	 my $translator  =  SQL::Translator->new(
	     parser	 => 'DBI',
	     dbh	 => $dbh,
	 );

       Or:

	 use SQL::Translator;

	 my $translator      =	SQL::Translator->new(
	     parser	     => 'DBI',
	     parser_args     => {
		 dsn	     => 'dbi:mysql:FOO',
		 db_user     => 'guest',
		 db_password => 'password',
	   }
	 );

DESCRIPTION

       This parser accepts an open database handle (or the arguments to create one) and queries the database directly for the information.

       The following are acceptable arguments:

       o   dbh

	   An open DBI database handle.  NB:  Be sure to create the database with the "FetchHashKeyName => 'NAME_lc'" option as all the DBI
	   parsers expect lowercased column names.

       o   dsn

	   The DSN to use for connecting to a database.

       o   db_user

	   The user name to use for connecting to a database.

       o   db_password

	   The password to use for connecting to a database.

       There is no need to specify which type of database you are querying as this is determined automatically by inspecting
       $dbh->{'Driver'}{'Name'}.  If a parser exists for your database, it will be used automatically; if not, the code will fail automatically
       (and you can write the parser and contribute it to the project!).

       Currently parsers exist for the following databases:

       o   MySQL

       o   SQLite

       o   Sybase

       o   PostgreSQL (still experimental)

       Most of these parsers are able to query the database directly for the structure rather than parsing a text file.  For large schemas, this
       is probably orders of magnitude faster than traditional parsing (which uses Parse::RecDescent, an amazing module but really quite slow).

       Though no Oracle parser currently exists, it would be fairly easy to query an Oracle database directly by using DDL::Oracle to generate a
       DDL for the schema and then using the normal Oracle parser on this.  Perhaps future versions of SQL::Translator will include the ability to
       query Oracle directly and skip the parsing of a text file, too.

AUTHOR

       Ken Y. Clark <kclark@cpan.org>.

SEE ALSO

       DBI, SQL::Translator.

perl v5.14.2							    2012-05-01					 SQL::Translator::Parser::DBI(3pm)

Check Out this Related Man Page

SQL::Translator::Parser::DBIx::Class(3) 		User Contributed Perl Documentation		   SQL::Translator::Parser::DBIx::Class(3)

NAME

       SQL::Translator::Parser::DBIx::Class - Create a SQL::Translator schema from a DBIx::Class::Schema instance

SYNOPSIS

	## Via DBIx::Class
	use MyApp::Schema;
	my $schema = MyApp::Schema->connect("dbi:SQLite:something.db");
	$schema->create_ddl_dir();
	## or
	$schema->deploy();

	## Standalone
	use MyApp::Schema;
	use SQL::Translator;

	my $schema = MyApp::Schema->connect;
	my $trans  = SQL::Translator->new (
	     parser	 => 'SQL::Translator::Parser::DBIx::Class',
	     parser_args => {
		 package => $schema,
		 add_fk_index => 0,
		 sources => [qw/
		   Artist
		   CD
		 /],
	     },
	     producer	 => 'SQLite',
	    ) or die SQL::Translator->error;
	my $out = $trans->translate() or die $trans->error;

DESCRIPTION

       This class requires SQL::Translator installed to work.

       "SQL::Translator::Parser::DBIx::Class" reads a DBIx::Class schema, interrogates the columns, and stuffs it all in an $sqlt_schema object.

       Its primary use is in deploying database layouts described as a set of DBIx::Class classes, to a database. To do this, see "deploy" in
       DBIx::Class::Schema.

       This can also be achieved by having DBIx::Class export the schema as a set of SQL files ready for import into your database, or passed to
       other machines that need to have your application installed but don't have SQL::Translator installed. To do this see "create_ddl_dir" in
       DBIx::Class::Schema.

PARSER OPTIONS

   add_fk_index
       Create an index for each foreign key.  Enabled by default, as having indexed foreign key columns is normally the sensible thing to do.

   sources
       Arguments: @class_names

       Limit the amount of parsed sources by supplying an explicit list of source names.

SEE ALSO

       SQL::Translator, DBIx::Class::Schema

AUTHORS

       See "CONTRIBUTORS" in DBIx::Class.

LICENSE

       You may distribute this code under the same terms as Perl itself.

perl v5.16.2							    2012-08-16				   SQL::Translator::Parser::DBIx::Class(3)

Linux and UNIX Man Pages

sql::translator::parser::dbi(3pm) [debian man page]

Check Out this Related Man Page