NAME<\/a> Moose::Cookbook::Legacy::Table_ClassMetaclass \u2212 Adding a “table” attribute to the metaclass<\/p>\n version 2.2014<\/p>\n package MyApp::Meta::Class; WARNING:<\/small> Subclassing metaclasses (as opposed to providing metaclass traits) is strongly discouraged. This recipe is provided solely for reference when encountering older code that does this.<\/b><\/p>\n In this recipe, we\u2019ll create a new metaclass which has a “table” attribute. This metaclass is for classes associated with a DBMS<\/small> table, as one might do for an ORM.<\/small><\/p>\n In this example, the table name is just a string, but in a real ORM<\/small> the table might be an object describing the table.<\/p>\n This really is as simple as the recipe ” SYNOPSIS”<\/small> shows. The trick is getting your classes to use this metaclass, and providing some sort of sugar for declaring the table. This is covered in Moose::Cookbook::Extending::Recipe2, which shows how to make a module like “Moose.pm” itself, with sugar like “has_table()”.<\/p>\n Using this Metaclass in Practice<\/b> my $table = MyApp::User\u2212>meta\u2212>table;<\/p>\n As long as “MyApp::User” has arranged to use “MyApp::Meta::Class” as its metaclass, this method call just works. If we want to be more careful, we can check the metaclass\u2019s class:<\/p>\n $table = MyApp::User\u2212>meta\u2212>table Creating custom metaclass is trivial. Using it is a little harder, and is covered in other recipes. We will also talk about applying traits to a class metaclass, which is a more flexible and cooperative implementation.<\/p>\n Moose::Cookbook::Meta::Recipe5 \u2212 The “table” attribute implemented as a metaclass trait<\/p>\n Moose::Cookbook::Extending::Recipe2 \u2212 Acting like Moose.pm and providing sugar Moose-style<\/p>\n \u2022<\/p>\n<\/td>\n Stevan Little \u2022<\/p>\n<\/td>\n Dave Rolsky \u2022<\/p>\n<\/td>\n Jesse Luehrs \u2022<\/p>\n<\/td>\n Shawn M Moore \u2022<\/p>\n<\/td>\n \u00d7\u00d7\u00d7\u00d7 \u00d7\u00a7\u00d7\u00d7\u2019\u00d7\u00d7 (Yuval Kogman) \u2022<\/p>\n<\/td>\n Karen Etheridge \u2022<\/p>\n<\/td>\n Florian Ragwitz \u2022<\/p>\n<\/td>\n Hans Dieter Pearcey \u2022<\/p>\n<\/td>\n
VERSION<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
THE METACLASS<\/a>
CONCLUSION<\/a>
SEE ALSO<\/a>
AUTHORS<\/a>
COPYRIGHT AND LICENSE<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
VERSION <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
use Moose;
extends ‘Moose::Meta::Class’;
has table => (
is => ‘rw’,
isa => ‘Str’,
);<\/p>\nDESCRIPTION <\/a> <\/h2>\n
THE METACLASS <\/a> <\/h2>\n
Accessing this new “table” attribute is quite simple. Given a class named “MyApp::User”, we could simply write the following:<\/p>\n
if MyApp::User\u2212>meta\u2212>isa(‘MyApp::Meta::Class’);<\/p>\nCONCLUSION <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
AUTHORS <\/a> <\/h2>\n
\n
\n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n