diff --git a/lib/SQL/Translator.pm b/lib/SQL/Translator.pm index 916f80b23..3847b5a43 100644 --- a/lib/SQL/Translator.pm +++ b/lib/SQL/Translator.pm @@ -959,7 +959,7 @@ analogously to C and C =head2 filters -Set or retreive the filters to run over the schema during the +Set or retrieve the filters to run over the schema during the translation, before the producer creates its output. Filters are sub routines called, in order, with the schema object to filter as the 1st arg and a hash of options (passed as a list) for the rest of the args. diff --git a/lib/SQL/Translator/Diff.pm b/lib/SQL/Translator/Diff.pm index c291ce47d..d8d6503f0 100644 --- a/lib/SQL/Translator/Diff.pm +++ b/lib/SQL/Translator/Diff.pm @@ -381,7 +381,7 @@ sub diff_table_constraints { sub diff_table_fields { my ($self, $src_table, $tar_table) = @_; - # List of ones ew've renamed from so we dont drop them + # List of ones we've renamed from so we don't drop them my %renamed_source_fields; for my $tar_table_field ( $tar_table->get_fields ) { @@ -442,7 +442,7 @@ sub diff_table_options { my ($a_name, undef, $b_name, undef) = ( %$a, %$b ); $a_name cmp $b_name; }; - # Need to sort the options so we dont get supruious diffs. + # Need to sort the options so we don't get spurious diffs. my (@src_opts, @tar_opts); @src_opts = sort $cmp $src_table->options; @tar_opts = sort $cmp $tar_table->options; @@ -471,7 +471,7 @@ SQL::Translator::Diff - determine differences between two schemas =head1 DESCRIPTION Takes two input SQL::Translator::Schemas (or SQL files) and produces ALTER -statments to make them the same +statements to make them the same =head1 SNYOPSIS @@ -572,7 +572,7 @@ I.e. the hash might look something like the following: C is called by the Diff code to allow the producer to normalize any data it needs to first. For example, the MySQL producer uses -this method to ensure that FK contraint names are unique. +this method to ensure that FK constraint names are unique. Basicaly any changes that need to be made to produce the SQL file for the schema should be done here, so that a diff between a parsed SQL file and (say) diff --git a/lib/SQL/Translator/Filter/Globals.pm b/lib/SQL/Translator/Filter/Globals.pm index d4dbfda63..497e40f57 100644 --- a/lib/SQL/Translator/Filter/Globals.pm +++ b/lib/SQL/Translator/Filter/Globals.pm @@ -104,7 +104,7 @@ sub filter { $schema->drop_table($gtbl); } - # Add globalis to tables + # Add globals to tables foreach my $tbl ( $schema->get_tables ) { foreach my $new_fld ( @global_fields ) { diff --git a/lib/SQL/Translator/Manual.pod b/lib/SQL/Translator/Manual.pod index d9e03813a..4be28b903 100644 --- a/lib/SQL/Translator/Manual.pod +++ b/lib/SQL/Translator/Manual.pod @@ -129,7 +129,7 @@ comma-separated file to an SQLite database, do the following: $ sqlt -f xSV --fs ',' -t SQLite foo.csv > foo-sqlite.sql -Additionally, there is a non-SQL represenation of relational schemas namely +Additionally, there is a non-SQL representation of relational schemas namely XML. Additionally, the only XML supported is our own version; however, it would be fairly easy to add an XML parser for something like the TorqueDB (http://db.apache.org/torque/) project. The actual parsing of XML should be @@ -148,7 +148,7 @@ operation performed by SQLFairy, so it may behoove you to serialize a parsed schema if you need to perform repeated conversions. For example, as part of a build process the author converts a MySQL schema first to YAML, then to PostgreSQL, Oracle, SQLite and Sybase. -Additionally, a variety of documention in HTML and images is produced. +Additionally, a variety of documentation in HTML and images is produced. This can be accomplished like so: $ sqlt -f MySQL -t YAML schema-mysql.sql > schema.yaml diff --git a/lib/SQL/Translator/Parser/SQLite.pm b/lib/SQL/Translator/Parser/SQLite.pm index 459f20384..ddc9ea438 100644 --- a/lib/SQL/Translator/Parser/SQLite.pm +++ b/lib/SQL/Translator/Parser/SQLite.pm @@ -737,7 +737,7 @@ sub parse { 1; # ------------------------------------------------------------------- -# All wholsome food is caught without a net or a trap. +# All wholesome food is caught without a net or a trap. # William Blake # ------------------------------------------------------------------- diff --git a/lib/SQL/Translator/Parser/XML/SQLFairy.pm b/lib/SQL/Translator/Parser/XML/SQLFairy.pm index 5cc37d144..7f54f3959 100644 --- a/lib/SQL/Translator/Parser/XML/SQLFairy.pm +++ b/lib/SQL/Translator/Parser/XML/SQLFairy.pm @@ -44,7 +44,7 @@ tags then the order the tags appear in the XML will be used. =head2 default_value Leave the attribute out all together to use the default in L. -Use empty quotes or 'EMPTY_STRING' for a zero lenth string. 'NULL' for an +Use empty quotes or 'EMPTY_STRING' for a zero length string. 'NULL' for an explicit null (currently sets default_value to undef in the Schema::Field obj). @@ -58,14 +58,14 @@ Doesn't take any extra parser args at the moment. =head1 LEGACY FORMAT -The previous version of the SQLFairy XML allowed the attributes of the the +The previous version of the SQLFairy XML allowed the attributes of the schema objects to be written as either xml attributes or as data elements, in any combination. While this allows for lots of flexibility in writing the XML the result is a great many possible XML formats, not so good for DTD writing, XPathing etc! So we have moved to a fixed version described in L. -This version of the parser will still parse the old formats and emmit warnings +This version of the parser will still parse the old formats and emit warnings when it sees them being used but they should be considered B. diff --git a/lib/SQL/Translator/Producer/ClassDBI.pm b/lib/SQL/Translator/Producer/ClassDBI.pm index f7994c991..4d26ee47b 100644 --- a/lib/SQL/Translator/Producer/ClassDBI.pm +++ b/lib/SQL/Translator/Producer/ClassDBI.pm @@ -106,7 +106,7 @@ sub produce { }; # - # Primary key may have a differenct accessor method name + # Primary key may have a different accessor method name # # if ( my $constraint = $table->primary_key ) { # my $field = ( $constraint->fields )[0]; diff --git a/lib/SQL/Translator/Producer/DiaUml.pm b/lib/SQL/Translator/Producer/DiaUml.pm index 9c7fa9650..187bd611c 100644 --- a/lib/SQL/Translator/Producer/DiaUml.pm +++ b/lib/SQL/Translator/Producer/DiaUml.pm @@ -22,7 +22,7 @@ SQL::Translator::Producer::DiaUml - Currently you will get one class (with the a table stereotype) generated per table in the schema. The fields are added as attributes of the classes and their datatypes set. It doesn't currently set any -of the relationships. It doesn't do any layout, all the classses are in one big +of the relationships. It doesn't do any layout, all the classes are in one big stack. However it is still useful as you can use the layout tools in Dia to automatically arrange them horizontally or vertically. @@ -64,7 +64,7 @@ Mark Addison Egrommit@users.sourceforge.netE. =head1 TODO -* Add the foriegn keys from the schema as UML relations. +* Add the foreign keys from the schema as UML relations. * Layout the classes. diff --git a/lib/SQL/Translator/Producer/GraphViz.pm b/lib/SQL/Translator/Producer/GraphViz.pm index c6c9c4de8..59529f0f5 100644 --- a/lib/SQL/Translator/Producer/GraphViz.pm +++ b/lib/SQL/Translator/Producer/GraphViz.pm @@ -113,7 +113,7 @@ constraints) =item * show_fields (DEFAULT: true) -If set to a true value, the names of the colums in a table will +If set to a true value, the names of the columns in a table will be displayed in each table's node =item * show_fk_only diff --git a/lib/SQL/Translator/Producer/Latex.pm b/lib/SQL/Translator/Producer/Latex.pm index f196ecd01..87369c253 100644 --- a/lib/SQL/Translator/Producer/Latex.pm +++ b/lib/SQL/Translator/Producer/Latex.pm @@ -22,7 +22,7 @@ SQL::Translator::Producer::Latex - Currently you will get one class (with the a table stereotype) generated per table in the schema. The fields are added as attributes of the classes and their datatypes set. It doesn't currently set any -of the relationships. It doesn't do any layout, all the classses are in one big +of the relationships. It doesn't do any layout, all the classes are in one big stack. However it is still useful as you can use the layout tools in Dia to automatically arrange them horizontally or vertically. diff --git a/lib/SQL/Translator/Producer/MySQL.pm b/lib/SQL/Translator/Producer/MySQL.pm index 1f8c541d6..6c06caa1d 100644 --- a/lib/SQL/Translator/Producer/MySQL.pm +++ b/lib/SQL/Translator/Producer/MySQL.pm @@ -69,11 +69,11 @@ compatibility. =item B, B -Set the tables default charater set and collation order. +Set the tables default character set and collation order. =item B, B -Set the fields charater set and collation order. +Set the fields character set and collation order. =back @@ -129,7 +129,7 @@ my %translate = ( ); # -# Column types that do not support lenth attribute +# Column types that do not support length attribute # my @no_length_attr = qw/ date time timestamp datetime year @@ -213,7 +213,7 @@ sub preprocess_schema { # Normalize constraint names here. my $c_name = $c->name; - # Give the constraint a name if it doesn't have one, so it doens't feel + # Give the constraint a name if it doesn't have one, so it doesn't feel # left out $c_name = $table->name . '_fk' unless length $c_name; @@ -876,7 +876,7 @@ sub batch_alter_table { my ($table, $diff_hash, $options) = @_; # InnoDB has an issue with dropping and re-adding a FK constraint under the - # name in a single alter statment, see: http://bugs.mysql.com/bug.php?id=13741 + # name in a single alter statement, see: http://bugs.mysql.com/bug.php?id=13741 # # We have to work round this. diff --git a/lib/SQL/Translator/Producer/PostgreSQL.pm b/lib/SQL/Translator/Producer/PostgreSQL.pm index bcfcb6f0d..5f898acec 100644 --- a/lib/SQL/Translator/Producer/PostgreSQL.pm +++ b/lib/SQL/Translator/Producer/PostgreSQL.pm @@ -831,7 +831,7 @@ sub alter_field $to_field->name) if ( !defined $new_default && defined $old_default ); - # add geometry column and contraints + # add geometry column and constraints push @out, add_geometry_column($to_field) if is_geometry($to_field); push @out, add_geometry_constraints($to_field) if is_geometry($to_field); diff --git a/lib/SQL/Translator/Producer/SQLite.pm b/lib/SQL/Translator/Producer/SQLite.pm index 2cccce22a..103c2deb6 100644 --- a/lib/SQL/Translator/Producer/SQLite.pm +++ b/lib/SQL/Translator/Producer/SQLite.pm @@ -464,7 +464,7 @@ sub batch_alter_table { my %temp_table_fields; do { local $table->{name} = $table_name . '_temp_alter'; - # We only want the table - dont care about indexes on tmp table + # We only want the table - don't care about indexes on tmp table my ($table_sql) = create_table($table, {no_comments => 1, temporary_table => 1}); push @sql,$table_sql; diff --git a/lib/SQL/Translator/Producer/TT/Base.pm b/lib/SQL/Translator/Producer/TT/Base.pm index 9c86f86e5..8155ff55f 100644 --- a/lib/SQL/Translator/Producer/TT/Base.pm +++ b/lib/SQL/Translator/Producer/TT/Base.pm @@ -205,7 +205,7 @@ The template to use, return a file name or a scalar ref of TT source, or an L. See L