Skip Menu |

This queue is for tickets about the DBIx-VersionedDDL CPAN distribution.

Report information
The Basics
Id: 62276
Status: resolved
Priority: 0/
Queue: DBIx-VersionedDDL

People
Owner: Nobody in particular
Requestors: JIRA [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Hello, this is really good and well thought module. I was just about to craft something like this together for my needs and then found your module. My idea for extension would be to allow to get the upgrade/downgrade scripts not only from local filesystem, but also for example from subversion repository. Maybe some sort plugin interface, that would make this modular? Would you consider something like this? Does that make sense? Kind Regards, Jiri
Hi This module performs a simple task simply. I'm not really keen to add much bloat to it. In my environments, I have a simple Perl script for releasing code, including running DDL upgrades. It updates the source from subversion before deploying the code. This is done outside of DBIx::VersionedDDL and works well for me. Having said that, if you can think of a simple way to add a plugin capability without breaking the existing API or adding significant complexity, then I will most likely be more than happy to add it. RT #61592 contains a proposal to add callback functionality, but I never heard back from the OP. Perhaps you could come up with an approach together. Dan
On Tue Oct 19 15:50:18 2010, DHORNE wrote: Show quoted text
> Hi > > This module performs a simple task simply. I'm not really keen to add > much bloat to it. In > my environments, I have a simple Perl script for releasing code, > including running DDL > upgrades. It updates the source from subversion before deploying the > code. This is done > outside of DBIx::VersionedDDL and works well for me.
That is an approach that makes perfect sense. Maybe I'll also do just some script to get the files before running DBIx::VersionedDDL. I'm just trying to think of unified interface/tool to push ddl updates in many different locations. Show quoted text
> > Having said that, if you can think of a simple way to add a plugin > capability without > breaking the existing API or adding significant complexity, then I > will most likely be more > than happy to add it. RT #61592 contains a proposal to add callback > functionality, but I > never heard back from the OP. Perhaps you could come up with an > approach together.
My, still somewhat vague, idea was to have a subclass with an interface of say 'list_files', 'get_file', 'store_file'. It could then load plugins via say MooseX::Object::Pluggable.
Functionality can be injected via OP's patch