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)

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

NAME

       SQL::Translator::Parser::SQLite - parser for SQLite

SYNOPSIS

	 use SQL::Translator;
	 use SQL::Translator::Parser::SQLite;

	 my $translator = SQL::Translator->new;
	 $translator->parser("SQL::Translator::Parser::SQLite");

DESCRIPTION

       This is a grammar for parsing CREATE statements for SQLite as described here:

	   http://www.sqlite.org/lang.html

       CREATE INDEX

       sql-statement ::=
	   CREATE [TEMP | TEMPORARY] [UNIQUE] INDEX index-name
	    ON [database-name .] table-name ( column-name [, column-name]* )
	    [ ON CONFLICT conflict-algorithm ]

       column-name ::=
	   name [ ASC | DESC ]

       CREATE TABLE

       sql-command ::=
	   CREATE [TEMP | TEMPORARY] TABLE table-name (
	       column-def [, column-def]*
	       [, constraint]*
	    )

       sql-command ::=
	   CREATE [TEMP | TEMPORARY] TABLE table-name AS select-statement

       column-def ::=
	   name [type] [[CONSTRAINT name] column-constraint]*

       type ::=
	   typename |
	    typename ( number ) |
	    typename ( number , number )

       column-constraint ::=
	   NOT NULL [ conflict-clause ] |
	   PRIMARY KEY [sort-order] [ conflict-clause ] |
	   UNIQUE [ conflict-clause ] |
	   CHECK ( expr ) [ conflict-clause ] |
	   DEFAULT value

       constraint ::=
	   PRIMARY KEY ( name [, name]* ) [ conflict-clause ]|
	   UNIQUE ( name [, name]* ) [ conflict-clause ] |
	   CHECK ( expr ) [ conflict-clause ]

       conflict-clause ::=
	   ON CONFLICT conflict-algorithm

       CREATE TRIGGER

       sql-statement ::=
	   CREATE [TEMP | TEMPORARY] TRIGGER trigger-name [ BEFORE | AFTER ]
	   database-event ON [database-name .] table-name
	   trigger-action

       sql-statement ::=
	   CREATE [TEMP | TEMPORARY] TRIGGER trigger-name INSTEAD OF
	   database-event ON [database-name .] view-name
	   trigger-action

       database-event ::=
	   DELETE |
	   INSERT |
	   UPDATE |
	   UPDATE OF column-list

       trigger-action ::=
	   [ FOR EACH ROW | FOR EACH STATEMENT ] [ WHEN expression ]
	       BEGIN
		   trigger-step ; [ trigger-step ; ]*
	       END

       trigger-step ::=
	   update-statement | insert-statement |
	   delete-statement | select-statement

       CREATE VIEW

       sql-command ::=
	   CREATE [TEMP | TEMPORARY] VIEW view-name AS select-statement

       ON CONFLICT clause

	   conflict-clause ::=
	   ON CONFLICT conflict-algorithm

	   conflict-algorithm ::=
	   ROLLBACK | ABORT | FAIL | IGNORE | REPLACE

       expression

       expr ::=
	   expr binary-op expr |
	   expr like-op expr |
	   unary-op expr |
	   ( expr ) |
	   column-name |
	   table-name . column-name |
	   database-name . table-name . column-name |
	   literal-value |
	   function-name ( expr-list | * ) |
	   expr (+) |
	   expr ISNULL |
	   expr NOTNULL |
	   expr [NOT] BETWEEN expr AND expr |
	   expr [NOT] IN ( value-list ) |
	   expr [NOT] IN ( select-statement ) |
	   ( select-statement ) |
	   CASE [expr] ( WHEN expr THEN expr )+ [ELSE expr] END

       like-op::=
	   LIKE | GLOB | NOT LIKE | NOT GLOB

AUTHOR

       Ken Youens-Clark <kclark@cpan.org>.

SEE ALSO

       perl(1), Parse::RecDescent, SQL::Translator::Schema.

perl v5.14.2							    2012-01-18				      SQL::Translator::Parser::SQLite(3pm)