use warnings;
use vars qw($VERSION);
-use base qw/DBIx::Class::Componentised/;
+use base qw/DBIx::Class::Componentised Class::Data::Accessor/;
-$VERSION = '0.03';
+sub mk_classdata { shift->mk_classaccessor(@_); }
+sub component_base_class { 'DBIx::Class' }
+# Always remember to do all digits for the version even if they're 0
+# i.e. first release of 0.XX *must* be 0.XX000. This avoids fBSD ports
+# brain damage and presumably various other packaging systems too
+
+$VERSION = '0.05006';
+
+sub MODIFY_CODE_ATTRIBUTES {
+ my ($class,$code,@attrs) = @_;
+ unless ($class->can('_attr_cache')) {
+ $class->mk_classdata('_attr_cache');
+ $class->_attr_cache({});
+ }
+ my $cache = $class->_attr_cache;
+ $class->_attr_cache->{$code} = [@attrs];
+ return ();
+}
1;
=head1 NAME
-DBIx::Class - Because the brain is a terrible thing to waste.
+DBIx::Class - Extensible and flexible object <-> relational mapper.
=head1 SYNOPSIS
=head1 DESCRIPTION
-This is a sql to oop mapper, inspired by the L<Class::DBI> framework,
+This is an SQL to OO mapper, inspired by the L<Class::DBI> framework,
and meant to support compability with it, while restructuring the
-insides, and making it possible to support some new features like
+internals and making it possible to support some new features like
self-joins, distinct, group bys and more.
-It's currently considered EXPERIMENTAL - bring this near a production
-database at your own risk! The API is *not* fixed yet, although most of
-the primitives should be good for the future and any API changes will be
-posted to the mailing list before they're committed.
+This project is still at an early stage, so the maintainers don't make
+any absolute promise that full backwards-compatibility will be supported;
+however, if we can without compromising the improvements we're trying to
+make, we will, and any non-compatible changes will merit a full justification
+on the mailing list and a CPAN developer release for people to test against.
The community can be found via -
=head1 QUICKSTART
-If you're using Class::DBI, replacing
+If you're using L<Class::DBI>, and want an easy and fast way of migrating to
+DBIx::Class, take a look at L<DBIx::Class::CDBICompat>.
+
+There are two ways of using DBIx::Class, the "simple" way and the "schema" way.
+The "simple" way of using DBIx::Class needs less classes than the "schema"
+way but doesn't give you the ability to easily use different database connections.
+
+Some examples where different database connections are useful are:
+
+different users with different rights
+different databases with the same schema.
+
+=head2 Simple
+
+First you need to create a base class which all other classes will inherit from.
+See L<DBIx::Class::DB> for information on how to do this.
+
+Then you need to create a class for every table you want to use with DBIx::Class.
+See L<DBIx::Class::Table> for information on how to do this.
+
+=head2 Schema
+
+With this approach, the table classes inherit directly from DBIx::Class::Core,
+although it might be a good idea to create a "parent" class for all table
+classes that inherits from DBIx::Class::Core and adds additional methods
+needed by all table classes, e.g. reading a config file or loading auto primary
+key support.
+
+Look at L<DBIx::Class::Schema> for information on how to do this.
+
+If you need more help, check out the introduction in the
+manual below.
+
+=head1 SEE ALSO
+
+=over 4
- use base qw/Class::DBI/;
+=item L<DBIx::Class::Core> - DBIC Core Classes
-with
+=item L<DBIx::Class::Manual> - User's manual
- use base qw/DBIx::Class/;
- __PACKAGE__->load_components(qw/CDBICompat Core DB/);
+=item L<DBIx::Class::CDBICompat> - L<Class::DBI> Compat layer
-will probably get you started.
+=item L<DBIx::Class::Schema>
-If you're using AUTO_INCREMENT for your primary columns, you'll also want
-yo load the approriate PK::Auto subclass - e.g.
+=item L<DBIx::Class::ResultSet>
- __PACKAGE__->load_components(qw/CDBICompat PK::Auto::SQLite Core DB/);
+=item L<DBIx::Class::ResultSource>
-(with is what ::Test::SQLite does to present the Class::DBI::Test::SQLite
-interface)
+=item L<DBIx::Class::Row> - row-level methods
-If you fancy playing around with DBIx::Class from scratch, then read the docs
-for ::Table and ::Relationship,
+=item L<DBIx::Class::PK> - primary key methods
- use base qw/DBIx::Class/;
- __PACKAGE__->load_components(qw/Core DB/);
+=item L<DBIx::Class::Relationship> - relationships between tables
-and have a look at t/lib/DBICTest.pm for a brief example.
+=back
=head1 AUTHOR
Dan Sully <daniel@cpan.org>
-davekam
+David Kamholz <dkamholz@cpan.org>
+
+Jules Bean
Marcus Ramberg <mramberg@cpan.org>
+Paul Makepeace
+
+CL Kao
+
+Jess Robinson
+
+Marcus Ramberg
+
+Will Hawes
+
+Todd Lipcon
+
+Daniel Westermann-Clark <danieltwc@cpan.org>
+
+Alexander Hartmaier <alex_hartmaier@hotmail.com>
+
+Zbigniew Lukasiak
+
+Nigel Metheringham <nigelm@cpan.org>
+
+Jesper Krogh
+
+Brandon Black
+
+Scotty Allen <scotty@scottyallen.com>
+
=head1 LICENSE
You may distribute this code under the same terms as Perl itself.
projects / dbsrgits/DBIx-Class.git / blobdiff