Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mojomojo::schema::resultset::page(3pm) [debian man page]

MojoMojo::Schema::ResultSet::Page(3pm)			User Contributed Perl Documentation		    MojoMojo::Schema::ResultSet::Page(3pm)

MojoMojo::Schema::ResultSet::Page - resultset methods on pages METHODS
path_pages ( $path_pages, $proto_pages ) = __PACKAGE__->path_pages( $path, $id ) Accepts a path in URL/Unix directory format, e.g. "/page1/page2". Paths are assumed to be absolute, so a leading slash (/) is not required. Returns a reference to an array of any pages that exist in the path, starting with "/", and an additional reference to an array of "proto page" hashes for any pages at the end of the path that do not exist. All paths include the root (/), which must exist, so a path of at least one element will always be returned. The "proto page" hash keys are shown in the example below, where we assume that "/blog" exists and "/blog/My_New_Entry" doesn't exist yet: { depth => 2, name => "my_new_entry", name_orig => "My_New_Entry", path => "/blog/My_New_Entry", }, path_pages_by_id @path_pages = __PACKAGE__->path_pages_by_id( $id ) Returns all the pages in the path to a page, given that page's id. parse_path @proto_pages = __PACKAGE__->parse_path( $path ) Create prototype page objects for each level in a given path. normalize_name ($name_orig, $name) = __PACKAGE__->normalize_name( $name_orig ) Strip superfluous spaces, convert the rest to _, then lowercase the result. resolve_path $an_resolve = __PACKAGE__->resolve_path( %args ) Takes the following args: path_pages proto_pages query_pages current_depth final_depth Returns true if the path can be resolved, or false otherwise. set_paths @pages = __PACKAGE__->set_paths( @pages ) Sets the path for multiple pages, either a subtree or a group of non-adjacent pages. create_path_pages $path_pages = __PACKAGE__->create_path_pages( %args ) Find or creates a list of path_pages. Returns a reference to an array of path_pages. open_gap $parent = __PACKAGE__->open_gap( $parent, $new_page_count ) Opens a gap in the nested set numbers to allow the inserting of new pages into the tree. Since nested sets number each node twice, the size of the gap is always twice the number of new pages. Also, since nested sets number the nodes from left to right, we determine what nodes to re-number according to the "rgt" column of the parent of the top-most new node. Returns a new parent object that is updated with the new "lft" "rgt" nested set numbers. create_page Create a new page in the wiki. perl v5.14.2 2011-07-20 MojoMojo::Schema::ResultSet::Page(3pm)

Check Out this Related Man Page

DBIx::Class::Schema::KiokuDB(3pm)			User Contributed Perl Documentation			 DBIx::Class::Schema::KiokuDB(3pm)

DBIx::Class::Schema::KiokuDB - Hybrid KiokuDB/DBIx::Class::Schema schema support. SYNOPSIS
Load this component into the schema: package MyApp::DB; use base qw(DBIx::Class::Schema); __PACKAGE__->load_components(qw(Schema::KiokuDB)); __PAKCAGE__->load_namespaces; Then load the DBIx::Class::KiokuDB component into every table that wants to refer to arbitrary KiokuDB objects: package MyApp::DB::Result::Album; use base qw(DBIx::Class::Core); __PACKAGE__->load_components(qw(KiokuDB)); __PACKAGE__->table('album'); __PACKAGE__->add_columns( id => { data_type => "integer" }, title => { data_type => "varchar" }, # the foreign key for the KiokuDB object: metadata => { data_type => "varchar" }, ); __PACKAGE__->set_primary_key('id'); # enable a KiokuDB rel on the column: __PACKAGE__->kiokudb_column('metadata'); Connect to the DSN: my $dir = KiokuDB->connect( 'dbi:SQLite:dbname=:memory:', schema => "MyApp::DB", create => 1, ); # get the connect DBIC schema instance my $schema = $dir->backend->schema; Then you can freely refer to KiokuDB objects from your "Album" class: $dir->txn_do(scope => 1, body => sub { $schema->resultset("Album")->create({ title => "Blah blah", metadata => $any_object, }); }); DESCRIPTION
This class provides the schema definition support code required for integrating an arbitrary DBIx::Class::Schema with KiokuDB::Backend::DBI. REUSING AN EXISTING DBIx::Class SCHEMA The example in the Synopis assumes that you want to first set up a KiokuDB and than link that to some DBIx::Class classes. Another use case is that you already have a configured DBIx::Class Schema and want to tack KiokuDB onto it. The trick here is to make sure to load the KiokuDB schema using "__PACKAGE__->define_kiokudb_schema()" in your Schema class: package MyApp::DB; use base qw(DBIx::Class::Schema); __PACKAGE__->load_components(qw(Schema::KiokuDB)); __PACKAGE__->define_kiokudb_schema(); __PAKCAGE__->load_namespaces; You can now get the KiokuDB directory handle like so: my $dir = $schema->kiokudb_handle; For a complete example take a look at t/autovivify_handle.t. USAGE AND LIMITATIONS
KiokuDB managed objects may hold references to row objects, resultsets (treated as saved searches, or results or cursor state is saved), result source handles, and the schema. Foreign DBIx::Class objects, that is ones that originated from a schema that isn't the underlying schema are currently not supported, but this limitation may be lifted in the future. All DBIC operations which may implicitly cause a lookup of a KIokuDB managed object require live object scope management, just as normal. It is reccomended to use "txn_do" in KiokuDB because that will invoke the appropriate transaction hooks on both layers, as opposed to just in DBIx::Class. SEE ALSO
DBIx::Class::KiokuDB, KiokuDB::Backend::DBI. perl v5.12.4 2011-10-04 DBIx::Class::Schema::KiokuDB(3pm)
Man Page