OT: Templating systems (was RE: [Catalyst] New default screen
matthew.lawrence at ehsbrann.com
Mon Oct 24 11:17:26 CEST 2005
Drew Taylor wrote:
> On 10/21/05, *Bill Moseley* <moseley at hank.org <mailto:moseley at hank.org>>
> On Fri, Oct 21, 2005 at 09:31:25AM +0100, Matthew Lawrence wrote:
> > There's an undocumented method in Class::DBI called
> make_read_only that
> > adds a _croak trigger to the create, delete and update methods.
> Is there a related method to remove those triggers?
> I don't believe there is. After all, having it work both ways would
> basically undo the whole purpose of having readonly objects. IIRC, all
> you have to do is dispose of the object and retrieve it again - no
> readonly triggers in sight.
Unless you define it in the class, that is. Which is reasonable for views.
Class::Trigger doesn't have a remove_trigger method, but it looks like
it should be fairly easy to break its encapsulation if you really need to.
More information about the Catalyst