Bumping version to 1.61

[dbsrgits/SQL-Translator.git] / lib / SQL / Translator / Parser / DBI / SQLite.pm

diff --git a/lib/SQL/Translator/Parser/DBI/SQLite.pm b/lib/SQL/Translator/Parser/DBI/SQLite.pm
index f752331..b86ed03 100644 (file)
--- a/lib/SQL/Translator/Parser/DBI/SQLite.pm
+++ b/lib/SQL/Translator/Parser/DBI/SQLite.pm
@@ -13,22 +13,22 @@ See SQL::Translator::Parser::DBI.
 Queries the "sqlite_master" table for schema definition.  The schema
 is held in this table simply as CREATE statements for the database
 objects, so it really just builds up a string of all these and passes
-the result to the regular SQLite parser.  Therefore there is no gain 
-(at least in performance) to using this module over simply dumping the 
+the result to the regular SQLite parser.  Therefore there is no gain
+(at least in performance) to using this module over simply dumping the
 schema to a text file and parsing that.
 
 =cut
 
 use strict;
+use warnings;
 use DBI;
 use SQL::Translator::Parser::SQLite;
 use Data::Dumper;
 
-use vars qw[ $DEBUG $VERSION @EXPORT_OK ];
-$VERSION = '1.59';
+our ( $DEBUG, @EXPORT_OK );
+our $VERSION = '1.61';
 $DEBUG   = 0 unless defined $DEBUG;
 
-# -------------------------------------------------------------------
 sub parse {
     my ( $tr, $dbh ) = @_;