X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass.pm;h=c26c9d6fc3f04f3b1b7beea92c8367617ae74dab;hb=23b2c49b17262ecf84307c9ffba88ed38ecc90cb;hp=6e335254471c7e998505b0997312be7f84b0e7ba;hpb=97ad6fb87893f91c8e7ab2bb043bff5e066d454c;p=dbsrgits%2FDBIx-Class.git diff --git a/lib/DBIx/Class.pm b/lib/DBIx/Class.pm index 6e33525..c26c9d6 100644 --- a/lib/DBIx/Class.pm +++ b/lib/DBIx/Class.pm @@ -11,7 +11,7 @@ our $VERSION; # $VERSION declaration must stay up here, ahead of any other package # declarations, as to not confuse various modules attempting to determine # this ones version, whether that be s.c.o. or Module::Metadata, etc -$VERSION = '0.08209'; +$VERSION = '0.08250'; $VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases @@ -40,6 +40,10 @@ BEGIN { # otherwise we are good : 0 , + + ASSERT_NO_INTERNAL_WANTARRAY => $ENV{DBIC_ASSERT_NO_INTERNAL_WANTARRAY} ? 1 : 0, + + IV_SIZE => $Config{ivsize}, }; if ($] < 5.009_005) { @@ -135,41 +139,16 @@ list below is sorted by "fastest response time": =back -=head1 HOW TO CONTRIBUTE - -Contributions are always welcome, in all usable forms (we especially -welcome documentation improvements). The delivery methods include git- -or unified-diff formatted patches, GitHub pull requests, or plain bug -reports either via RT or the Mailing list. Contributors are generally -granted full access to the official repository after their first patch -passes successful review. - -=for comment -FIXME: Getty, frew and jnap need to get off their asses and finish the contrib section so we can link it here ;) - -This project is maintained in a git repository. The code and related tools are -accessible at the following locations: - -=over - -=item * Official repo: L - -=item * Official gitweb: L - -=item * GitHub mirror: L - -=item * Authorized committers: L - -=item * Travis-CI log: L +=head1 SYNOPSIS -=for html -
↪ Stable branch CI status: +For the very impatient: L -=back +This code in the next step can be generated automatically from an existing +database, see L from the distribution C. -=head1 SYNOPSIS +=head2 Schema classes preparation -Create a schema class called MyApp/Schema.pm: +Create a schema class called F: package MyApp::Schema; use base qw/DBIx::Class::Schema/; @@ -179,7 +158,7 @@ Create a schema class called MyApp/Schema.pm: 1; Create a result class to represent artists, who have many CDs, in -MyApp/Schema/Result/Artist.pm: +F: See L for docs on defining result classes. @@ -194,7 +173,7 @@ See L for docs on defining result classes. 1; A result class to represent a CD, which belongs to an artist, in -MyApp/Schema/Result/CD.pm: +F: package MyApp::Schema::Result::CD; use base qw/DBIx::Class::Core/; @@ -207,6 +186,8 @@ MyApp/Schema/Result/CD.pm: 1; +=head2 API usage + Then you can use these classes in your application's code: # Connect to your database. @@ -275,7 +256,8 @@ that allows abstract encapsulation of database operations. It aims to make representing queries in your code as perl-ish as possible while still providing access to as many of the capabilities of the database as possible, including retrieving related records from multiple tables in a single query, -JOIN, LEFT JOIN, COUNT, DISTINCT, GROUP BY, ORDER BY and HAVING support. +C, C, C, C, C, C and +C support. DBIx::Class can handle multi-column primary and foreign keys, complex queries and database-level paging, and does its best to only query the @@ -288,8 +270,8 @@ and thread-safe out of the box (although L). This project is still under rapid development, so large new features may be -marked EXPERIMENTAL - such APIs are still usable but may have edge bugs. -Failing test cases are *always* welcome and point releases are put out rapidly +marked B - such APIs are still usable but may have edge bugs. +Failing test cases are I welcome and point releases are put out rapidly as bugs are found and fixed. We do our best to maintain full backwards compatibility for published @@ -301,6 +283,38 @@ The test suite is quite substantial, and several developer releases are generally made to CPAN before the branch for the next release is merged back to trunk for a major release. +=head1 HOW TO CONTRIBUTE + +Contributions are always welcome, in all usable forms (we especially +welcome documentation improvements). The delivery methods include git- +or unified-diff formatted patches, GitHub pull requests, or plain bug +reports either via RT or the Mailing list. Contributors are generally +granted full access to the official repository after their first patch +passes successful review. + +=for comment +FIXME: Getty, frew and jnap need to get off their asses and finish the contrib section so we can link it here ;) + +This project is maintained in a git repository. The code and related tools are +accessible at the following locations: + +=over + +=item * Official repo: L + +=item * Official gitweb: L + +=item * GitHub mirror: L + +=item * Authorized committers: L + +=item * Travis-CI log: L + +=for html +↪ Stable branch CI status: + +=back + =head1 AUTHOR mst: Matt S. Trout @@ -338,7 +352,7 @@ arcanez: Justin Hunter ash: Ash Berlin -bert: Norbert Csongradi +bert: Norbert Csongrádi blblack: Brandon L. Black @@ -388,6 +402,8 @@ dyfrgi: Michael Leuchtenburg edenc: Eden Cardim +ether: Karen Etheridge + felliott: Fitz Elliott freetime: Bill Moseley @@ -482,6 +498,8 @@ perigrin: Chris Prather peter: Peter Collingbourne +Peter Siklósi + Peter Valdemar MErch phaylon: Robert Sedlacek