Hi, Since 0.50, Padre includes a fork of ORLite::Migrate as Padre::DB::Migrate. Quite some time passed and the fork is still there. What is the perspective of using the 'main' ORLite::Migrate again?
I ask this because code duplication can increase downstream maintenance cost when a bad bug (for example a security-related one) needs to be fixed in multiple places.
signature.asc
Description: Digital signature
_______________________________________________ Padre-dev mailing list [email protected] http://mail.perlide.org/mailman/listinfo/padre-dev
