X-Git-Url: http://git.freeside.biz/gitweb/?a=blobdiff_plain;f=DBSchema.pm;h=43baaafc921d79fda56e34a0f38140322cfc90ec;hb=ca90218a5e9b23b9ce52e3cfb942f13c9c1429d7;hp=12eda6d270e2d00d8c4d7093bd9a4cbe1f5ac055;hpb=d2de365ce67040de0511073417db40e5550d63be;p=DBIx-DBSchema.git

diff --git a/DBSchema.pm b/DBSchema.pm
index 12eda6d..43baaaf 100644
--- a/DBSchema.pm
+++ b/DBSchema.pm
@@ -292,7 +292,7 @@ sub sql_update_schema {
   # should eventually drop tables not in $new
 
   warn join("\n", @r). "\n"
-    if $DEBUG;
+    if $DEBUG > 1;
 
   @r;
   
@@ -500,13 +500,6 @@ or deal with deleted or modified columns yet.
 
 Need to port and test with additional databases
 
-On schema updates, index changes are not as efficent as they could be,
-especially with large data sets.  Specifically, we don't currently recognize
-existing indices with different/"wrong" names that we could use "ALTER INDEX
-name RENAME TO new_name" on, and instead drop the "wrongly named" index and
-re-build a new one.  Since these are indices and not columns, its not a huge
-deal, everything turns out right in the end, though inefficient.
-
 Each DBIx::DBSchema object should have a name which corresponds to its name
 within the SQL database engine (DBI data source).