X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FSQL%2FTranslator%2FProducer%2FTTSchema.pm;h=ee5a7f1d42ffc0e2037a892933bf7145324588eb;hb=d4f84dd192edc7a64a0b1a9923f1bafc0bc5ef9d;hp=29b1a9a3cc3bef74f01f2a6e20309e72fcd52c36;hpb=2304f604779b32141b1d5b09bef2d7c169411a92;p=dbsrgits%2FSQL-Translator.git diff --git a/lib/SQL/Translator/Producer/TTSchema.pm b/lib/SQL/Translator/Producer/TTSchema.pm index 29b1a9a..ee5a7f1 100644 --- a/lib/SQL/Translator/Producer/TTSchema.pm +++ b/lib/SQL/Translator/Producer/TTSchema.pm @@ -1,9 +1,9 @@ package SQL::Translator::Producer::TTSchema; # ------------------------------------------------------------------- -# $Id: TTSchema.pm,v 1.7 2004-11-16 09:15:36 boconnor Exp $ +# $Id: TTSchema.pm 1440 2009-01-17 16:31:57Z jawnsy $ # ------------------------------------------------------------------- -# Copyright (C) 2002-4 SQLFairy Authors +# Copyright (C) 2002-2009 SQLFairy Authors # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License as @@ -24,7 +24,7 @@ package SQL::Translator::Producer::TTSchema; =head1 NAME -SQL::Translator::Producer::TTSchema - +SQL::Translator::Producer::TTSchema - Produces output using the Template Toolkit from a SQL schema =head1 SYNOPSIS @@ -35,8 +35,17 @@ SQL::Translator::Producer::TTSchema - filename => 'foo_schema.sql', to => 'TTSchema', producer_args => { - ttargs => {}, - ttfile => 'foo_template.tt', + ttfile => 'foo_template.tt', # Template file to use + + # Extra template variables + ttargs => { + author => "Mr Foo", + }, + + # Template config options + ttargs => { + INCLUDE_PATH => '/foo/templates', + }, }, ); print $translator->translate; @@ -46,10 +55,10 @@ SQL::Translator::Producer::TTSchema - Produces schema output using a given Template Tookit template. It needs one additional producer_arg of C which is the file -name of the template to use. This template will be passed a single -argument called C, which is the -C object, which you can then use to -walk the schema via the methods documented in that module. +name of the template to use. This template will be passed a variable +called C, which is the C object +created by the parser. You can then use it to walk the schema via the +methods documented in that module. Here's a brief example of what the template could look like: @@ -65,17 +74,25 @@ Here's a brief example of what the template could look like: See F for a more complete example. -You can also set any of the options used to initiallize the Template object by -adding them to your producer_args. See Template Toolkit docs for details of +The template will also get the set of extra variables given as a hashref via the +C producer arg. + +You can set any of the options used to initiallize the Template object by +adding a tt_conf producer_arg. See Template Toolkit docs for details of the options. +(Note that the old style of passing this config directly in the producer args +has been deprecated). + $translator = SQL::Translator->new( to => 'TT', producer_args => { ttfile => 'foo_template.tt', ttargs => {}, - INCLUDE_PATH => '/foo/templates/tt', - INTERPOLATE => 1, + tt_conf = { + INCLUDE_PATH => '/foo/templates/tt', + INTERPOLATE => 1, + } }, ); @@ -86,14 +103,32 @@ schema into MySQL's syntax, your own HTML documentation, your own Class::DBI classes (or some other code) -- the opportunities are limitless! +=head2 Producer Args + +=over 4 + +=item ttfile + +The template file to generate the output with. + +=item tt_vars + +A hash ref of extra variables you want to add to the template. + +=item tt_conf + +A hash ref of configuration options to pass to the L