sql::translator::filter::names(3pm) [debian man page]

SQL::Translator::Filter::Names(3pm)			User Contributed Perl Documentation		       SQL::Translator::Filter::Names(3pm)

NAME

       SQL::Translator::Filter::Names - Tweak the names of schema objects.

SYNOPSIS

	 #! /usr/bin/perl -w
	 use SQL::Translator;

	 # Lowercase all table names and upper case the first letter of all field
	 # names. (MySql style!)
	 #
	 my $sqlt = SQL::Translator->new(
	     filename => @ARGV,
	     from     => 'MySQL',
	     to       => 'MySQL',
	     filters => [
	       Names => {
		   'tables' => 'lc',
		   'fields' => 'ucfirst',
	       },
	     ],
	 ) || die "SQLFairy error : ".SQL::Translator->error;
	 print($sqlt->translate) || die "SQLFairy error : ".$sqlt->error;

DESCRIPTION

SEE ALSO

       perl(1), SQL::Translator

BUGS

TODO

       Name Groups
	   Define a bunch of useful groups to run the name filters over. e.g. all, fkeys, pkeys etc.

       More Functions
	   e.g. camelcase, titlecase, single word etc.	Also a way to pass in a regexp.

	   May also want a way to pass in arguments for the func e.g. prefix.

       Multiple Filters on the same name (filter order)?
	   Do we actually need this, you could just run lots of filters. Would make adding func args to the interface easier.

	       filters => [
		   [ 'Names', { all => 'lc' } ],
		   [ 'Names', {
		       tables => 'lc',
		       fields => 'ucfirst',
		   } ],
	       ],

	   Mind you if you could give the filter a list this wouldn't be a problem!

	       filters => [
		   [ 'Names',
		       all    => 'lc'
		       fields => 'ucfirst',
		   ],
	       ],

	   Which is nice. Might have to change the calling conventions for filters.  Would also provide an order to run the filters in rather than
	   having to hard code it into the filter it's self.

AUTHOR

perl v5.14.2							    2012-01-18				       SQL::Translator::Filter::Names(3pm)

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

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.14.2							    2011-05-10				 SQL::Translator::Parser::DBIx::Class(3pm)