KiokuDB::Backend::DBI - DBI backend for KiokuDB River stage one • 6 direct dependents • 8 total dependents

This backend for KiokuDB leverages existing DBI accessible databases. The schema is based on two tables, "entries" and "gin_index" (the latter is only used if a Search::GIN extractor is specified). The "entries" table has two main columns, "id" and "...

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

KiokuDB::Backend::DBI::Schema River stage one • 6 direct dependents • 8 total dependents

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

DBIx::Class::KiokuDB - Refer to KiokuDB objects from DBIx::Class tables. River stage one • 6 direct dependents • 8 total dependents

This DBIx::Class component provides the code necessary for DBIx::Class::Row objects to refer to KiokuDB objects stored in KiokuDB::Backend::DBI....

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

DBIx::Class::Schema::KiokuDB - Hybrid KiokuDB/DBIx::Class::Schema schema support. River stage one • 6 direct dependents • 8 total dependents

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 Kio...

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

DBIx::Class::KiokuDB::EntryProxy - A proxying result class for KiokuDB objects River stage one • 6 direct dependents • 8 total dependents

This class implements the necessary glue to properly inflate resultsets for KiokuDB object into proper instances using KiokuDB....

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

KiokuDB::TypeMap::Entry::DBIC::Row - KiokuDB::TypeMap::Entry for DBIx::Class::Row objects. River stage one • 6 direct dependents • 8 total dependents

DBIx::Class::Row objects are resolved symbolically using the special ID format: dbic:row:$json The $json string is a serialization of: [ $result_source_name, @primary_key_values ] The row objects are not actually written to the KiokuDB storage, as th...

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

KiokuDB::TypeMap::Entry::DBIC::Schema - KiokuDB::TypeMap::Entry for DBIx::Class::Schema objects. River stage one • 6 direct dependents • 8 total dependents

This typemap entry handles references to DBIx::Class::Schema as a scoped singleton. The ID of the schema is always "dbic:schema". References to DBIx::Class::Schema objects which are not a part of the underlying DBIx::Class layout are currently not su...

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

KiokuDB::TypeMap::Entry::DBIC::ResultSet - KiokuDB::TypeMap::Entry for DBIx::Class::ResultSet objects River stage one • 6 direct dependents • 8 total dependents

The result set is cloned, the clone will have its cache cleared, and then it is simply serialized normally. This is the only DBIx::Class related object that is literally stored in the database, as it represents a memory resident object, not a databas...

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

KiokuDB::TypeMap::Entry::DBIC::ResultSource - KiokuDB::TypeMap::Entry for DBIx::Class::ResultSource objects. River stage one • 6 direct dependents • 8 total dependents

This tyepmap entry resolves result source handles symbolically by name. References to the handle receive a special ID in the form: dbic:schema:rs:$name and are not actually written to storage. Looking up such an ID causes the backend to dynamically s...

DOY/KiokuDB-Backend-DBI-1.23 - 31 Mar 2014 20:06:52 UTC

KiokuDB - Object Graph storage engine River stage two • 22 direct dependents • 24 total dependents

KiokuDB is a Moose based frontend to various data stores, somewhere in between Tangram and Pixie. Its purpose is to provide persistence for "regular" objects with as little effort as possible, without sacrificing control over how persistence is actua...

DOY/KiokuDB-0.57 - 25 Mar 2014 21:04:20 UTC

Task::KiokuDB - Install KiokuDB and related modules. River stage one • 1 direct dependent • 1 total dependent

This bundle installs KiokuDB and depending on the environment several additional components....

DOY/Task-KiokuDB-0.07 - 02 May 2012 21:43:42 UTC

Dancer::Session::KiokuDB - KiokuDB Dancer session backend River stage zero No dependents

When you want to save session information, you can pick from various session backends, and they each determine how the session information will be saved. You can use Dancer::Session::Cookie, Dancer::Session::MongoDB or... you use Dancer::Session::Kio...

XSAWYERX/Dancer-Session-KiokuDB-0.05 - 10 Mar 2011 12:36:33 UTC

KiokuDB::Backend::Role::TXN - Backend level transaction support. River stage two • 22 direct dependents • 24 total dependents

This API is inspired by standard database transactions much like you get with DBI. This is the low level interface required by "txn_do" in KiokuDB....

DOY/KiokuDB-0.57 - 25 Mar 2014 21:04:20 UTC

13 results (0.036 seconds)