60 results (0.522 seconds)
Dave Rolsky
Documentation
Alzabo::FAQ - Frequently Asked Questions
Alzabo::QuickRef - A quick reference to methods in the Alzabo classes
Modules
Alzabo - A data modelling tool and RDBMS-OO mapper
Alzabo::BackCompat - Convert old data structures
Alzabo::ChangeTracker - Saves a set of changes as callbacks that can be backed out if needed
Alzabo::Column - Column objects
Alzabo::ColumnDefinition - Holds the type attribute for a column
Alzabo::Config - Alzabo configuration information
Alzabo::Create - Loads all Alzabo::Create::* classes
Alzabo::Create::Column - Column objects for use in schema creation
Alzabo::Create::ColumnDefinition - Column definition object for schema creation
Alzabo::Create::ForeignKey - Foreign key objects for schema creation.
Alzabo::Create::Index - Index objects for schema creation
Alzabo::Create::Schema - Schema objects for schema creation
Alzabo::Create::Table - Table objects for schema creation
Alzabo::Driver - Alzabo base class for RDBMS drivers
Alzabo::Driver::MySQL - MySQL specific Alzabo driver subclass
Alzabo::Driver::PostgreSQL - PostgreSQL specific Alzabo driver subclass
Alzabo::Exceptions - Creates all exception subclasses used in Alzabo.
Alzabo::ForeignKey - Foreign key (relation) objects
Alzabo::Index - Index objects
Alzabo::MethodMaker - Auto-generate useful methods based on an existing schema
Alzabo::ObjectCache - A simple in-memory cache for row objects.
Alzabo::ObjectCache::Store::BerkeleyDB - Cache objects in a BerkeleyDB file
Alzabo::ObjectCache::Store::LRU - Make any storage module an LRU
Alzabo::ObjectCache::Store::Memory - Cache objects in memory
Alzabo::ObjectCache::Store::Null - Doesn't really store anything
Alzabo::ObjectCache::Store::RDBMS - Cache objects in an RDBMS backend
Alzabo::ObjectCache::Sync - Base class for syncing classes
Alzabo::ObjectCache::Sync::BerkeleyDB - Uses a DBM file to sync object caches
Alzabo::ObjectCache::Sync::DBM - Base class for syncing modules that use DBM files
Alzabo::ObjectCache::Sync::DB_File - Uses a Berkeley DB file to sync object caches
Alzabo::ObjectCache::Sync::IPC - Uses a IPC file to sync object caches
Alzabo::ObjectCache::Sync::Mmap - Uses a IPC file to sync object caches
Alzabo::ObjectCache::Sync::Null - No inter-process cache syncing
Alzabo::ObjectCache::Sync::RDBMS - Uses an RDBM backend to sync object caches
Alzabo::ObjectCache::Sync::SDBM_File - Uses an SDBM file to sync object caches
Alzabo::RDBMSRules - Base class for Alzabo RDBMS rulesets
Alzabo::RDBMSRules::MySQL - MySQL specific database rules.
Alzabo::RDBMSRules::PostgreSQL - PostgreSQL specific database rules
Alzabo::Runtime - Loads all Alzabo::Runtime::* classes
Alzabo::Runtime::CachedRow - Cached row objects
Alzabo::Runtime::Column - Column objects
Alzabo::Runtime::ColumnDefinition - Column definition objects
Alzabo::Runtime::Cursor - Base class for Alzabo cursors
Alzabo::Runtime::ForeignKey - Foreign key objects
Alzabo::Runtime::Index - Index objects
Alzabo::Runtime::JoinCursor - Cursor that returns arrays of Alzabo::Runtime::Row objects
Alzabo::Runtime::PotentialRow - Row objects that aren't yet in the database
Alzabo::Runtime::Row - Row objects
Alzabo::Runtime::RowCursor - Cursor that returns Alzabo::Runtime::Row objects
Alzabo::Runtime::Schema - Schema objects
Alzabo::Runtime::Table - Table objects
Alzabo::SQLMaker - Alzabo base class for RDBMS drivers
Alzabo::SQLMaker::MySQL - Alzabo SQL making class for MySQL
Alzabo::SQLMaker::PostgreSQL - Alzabo SQL making class for PostgreSQL
Alzabo::Schema - Schema objects
Alzabo::Table - Table objects
Provides
Alzabo::DriverStatement in lib/Alzabo/Driver.pm
Alzabo::Exception::Driver in lib/Alzabo/Exceptions.pm
Alzabo::SQLMaker::Function in lib/Alzabo/SQLMaker.pm
Changes for version 0.65
    • INCOMPATIBILITIES:
    • Alzabo now uses the natively created Postgres sequence for SERIAL
    • columns. If you have existing Alzabo code with SERIAL columns that is
    • using the Alzabo-created sequence, then this release will break things
    • for you. One easy fix is to simply drop the existing Postgres-created
    • sequence and recreate it with a new starting number one higher than
    • the highest row already in existence. So if your hightest "foo_id"
    • value in the "Foo" table is 500, you would do this: DROP SEQUENCE foo_foo_id_seq; CREATE SEQUENCE foo_foo_id_seq START 501;
    • The Alzabo::Table->primary_key method is now context-sensitive,
    • returning a single column object in scalar context.
    • The data browser is no longer installed, until such time as I can
    • rewrite it to be more useful.
    • DEPRECATIONS:
    • The Alzabo::Create::Schema->add_relation method has been renamed as
    • Alzabo::Create::Schema->add_relationship.
    • ENHANCEMENTS:
    • Check out the mason/widgets directory for some handy widgets that
    • can help integrate Mason and Alzabo in useful ways. These aren't
    • really well-documented yet but may be useful for playing with. More
    • widgets will be included in future releases (I hope).
    • When creating a relationship between tables in the schema creator,
    • you can now let Alzabo figure out which columns to use instead of
    • choosing them yourself. For most relationships, Alzabo will simply do
    • the right thing, adding a column to one of the tables as needed.
    • The problems running the tests with Postgres should now be fixed.
    • Fix stupid and inefficient internal handling of "SELECT DISTINCT"
    • queries. Now Alzabo simply lets the database handle this, the way it
    • should have in the first place.
    • The Alzabo::Runtime::Schema and Alzabo::Runtime::Table ->function
    • and ->select methods now allow you to select scalars so you can do
    • things like SELECT 1 FROM Foo WHERE ... in order to test for the
    • existence of a row.
    • Added Alzabo::Table->primary_key_size method, which indicates how
    • many columns participate in the table's primary key.
    • Added Alzabo::Runtime::Schema->row_count. Suggested by Daniel
    • Gaspani.
    • Alzabo now detects older versions of schemas and transparently
    • updates them. This will work for all schemas created with version



Hosting generously
sponsored by Bytemark