Changeset 2660

Show
Ignore:
Timestamp:
06/30/08 20:46:39 (20 months ago)
Author:
mpaschal
Message:

Some questions about this new code
BugzID: 80404

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • branches/release-41/lib/MT/Upgrade.pm

    r2637 r2660  
    10111011        next TYPE if !$class->has_meta();  # nothing to upgrade 
    10121012 
     1013        # TODO: what is this supposed to mean? 
    10131014        my $t = $type; 
    10141015        my $class_type = $class->properties->{class_type}; 
     
    10211022            # If there's no appropriate superclass, go to update with the class 
    10221023            # we have, not the class we want. 
     1024            # TODO: if we're checking against the registry type without modifying it, why are we looking for a better object class first? 
    10231025            next TYPE if $added_step{$type};  # already got that one 
    10241026        } 
     
    10271029        } 
    10281030 
     1031        # TODO: why is this no longer the representative type for a table? that makes us upgrade tables multiple times 
    10291032        my %step_param = ( type => $t ); 
     1033        # TODO: can't we just make this a different upgrade step? 
    10301034        $step_param{plugindata} = 1 
    10311035            if ( $class eq 'MT::Category' ) || ( $class eq 'MT::Folder' ); 
     
    11251129    my $stmt = $dbd->sql_class->new; 
    11261130 
    1127     # assumes 'meta' is the meta column name; should be for all core types 
    1128     # we are processing 
    11291131    my $meta_col = $param{meta_column} || 'meta'; 
    11301132