--- John Siracusa <[EMAIL PROTECTED]> wrote:
> sub add_columns
> {
> my($self) = shift;
>
> my @added_columns = $self->SUPER::add_columns(@_);
>
> foreach my $column (@added_columns )
> {
> $self->alias_column($column->name => '_' . $column->name)
> unless($self->class->is_public($column));
> }
>
> return @added_columns ;
> }
Hey, thanks for the clarification.
> If I understand your intent correctly, and you really never want to
> be
> able to set certain columns at all from Perl-land, another possible
> technique is to simply create accessor-only methods for them. That
> is, just "get" methods instead of the usual "get_set" methods.
That sounds reasonable. What I had done was set up the 'save',
'update', 'delete', and 'insert' methods to throw exceptions.
I didn't see it in the docs, but is there anything akin to 'mutator'
metadata which would let me do something like the following?
foreach my $method ( $class->mutators ) {
$self->make_override( $method );
}
The 'mutators' would return all 'set_*' type methods along with the
'update', 'delete', etc. methods.
And thanks for your response. I'm really liking what I see in Rose :)
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rose-db-object
