Update Plugin Version in Config.DB for enabled plugins only, please add to trunk :)

[bowtie]

I noticed that the Plugins DB was not being updated when a plugin version changed, so here is a fix. for active plugins only.

lib/Padre/PluginManager.pm

@@ -656 +656 @@
             $locale->AddCatalogLookupPathPrefix($dir);
         }
     }
+    
+    # update version for enabled plugins
+    Padre::DB::Plugin->update_version(
+        $module => $module->VERSION,
+    );
 
     # FINALLY we can enable the plug-in
     $plugin->enable;
@@ -1241 +1246 @@
 # LICENSE
 # This program is free software; you can redistribute it and/or
 # modify it under the same terms as Perl 5 itself.
-

lib/Padre/DB/Plugin.pm

@@ -26 +26 @@
     );
 }
 
+# Set version for an object
+sub update_version {
+    Padre::DB->do(
+        'update plugin set version = ? where name = ?', {},
+        $_[2], $_[1],
+    );
+}
+
 1;
 
 __END__
@@ -259 +267 @@
 
 Returns true, or throws an exception on error.
 
+=head2 update_version
+
+    Padre::DB::Plugin->update_version(
+        $module => $module->VERSION,
+    );
+
+Update Version of Plugin, enables Config.DB to be keeped upto date.
+
 =head1 ACCESSORS
 
 =head2 name

a P-P-Cookbook by product :)

[szabgab]

It seems like an easy fix but I wonder why do we care to keep the version numbers in the database? Where do we use them?

[bowtie]

it's only when you look at ConfigDB via Cookbook do you see it's wrong,
also do we not want all plugins to use ConfigDB and config.ymal for Padre settings?
We can also now check if a previous version was installed.

If we arn't going to update it, then why do we need it.

this would mean that Version and Config are superfluous attributes then :(

[bowtie]

This has bean implemented in r14980, not as is, but with modification by Alias++