| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
3.0.14 Jan 03 2006
- Fix breakage with mutator_name (Ask Bj�rn Hansen)
3.0.13 Dec 15 2005
- Use DBI's last_insert_id() where available (David Steinbrunner)
- Cope better with deleting through a might_have (Rob Brown)
- Allow setting a false value or NULL in a might_have (Brad Bowman)
3.0.12 Nov 04 2005
- Use Clone instead of dclone for cloning meta info to reduce required
perl version (Juan Camacho) and allow for closures (RT#15498)
- Remove lots of old deprecations
3.0.11 Oct 23 2005
- search through a has_many can now take hash_ref
- Fix documentation for SQL wildcards (RT#15145)
3.0.10 Oct 7 2005
- Set Storable::Deparse so that has_a subrefs can be cloned (Will Ross)
- Use shorter version of mk_classdata
- Include t/24 which was accidentally left out of MANIFEST in 3.0.9
3.0.9 Sep 23 2005
- Fixed bug with shared meta_info (Will Ross)
- create() has been renamed to insert() to make it much clearer that
it corresponds to an SQL INSERT rather than lots of different ideas
as to what create() might mean. create() still (silently) works. It
will give 'deprecated' warnings from 3.2.0 and will be removed no
earlier than 3.4.0.
The before/after create triggers have NOT been renamed yet as I'm
rethinking some of that. We'll probably end up with more trigger
points. Comments and suggestions welcome.
3.0.8 Sep 20 2005
- constraint exceptions now set their 'data' (Dan Collis Puro)
- method created by has_many can now override method in parent class
(reported by Christopher H. Laco)
- factored out transform_sql for easier modification
3.0.7 Sep 17 2005
- Make Column responsible for accessor() and mutator() so they can be
set up declaratively as well as programmatically (this means the
second argument to accessor_name and mutator_name is now a Column
object rather than its name, so you may need to check your case
sensitivity)
- Rename accessor/mutator_name to accessor/mutator_name_for
- Document that order_by clauses in sort() are passed through
- Make one-shot 'Essential' set up slightly more explicit in docs
(Adam Kennedy)
- Fix HasMany warning typo (argumemt) (Dan Friedman)
- Remove obsolete SearchGenerator code which had leaked out
3.0.6 Sep 16 2005
- constrain_column can now take subref constraint
- Document DBD::AnyData and FreeTDS issues (Matt Trout)
- Factor out database error handling to _db_error()
- Switch to Class::Accessor::Fast in Column and Relationship
3.0.5 Sep 14 2005
- has_many can take compile time constraints (Cees Hek)
- has_many can take a cascading delete strategy (deprecating the old,
undocumented, 'no_cascade_delete' option)
- columns() can take Class::DBI::Column objects directly
which can now in turn take options, thus allowing things like:
__PACKAGE__->columns(dates => Class::DBI::Column->new(
tdate => { placeholder => 'IF(1, CURDATE(), ?)' }
)
3.0.4 Sep 13 2005
Pre-Reqs
- Note requirement for Scalar::Util 1.08+ (for refaddr)
Refactorings
- Move to pluggable Search interface
(includes reworking of search approach per Tim Bunce)
3.0.3 Sep 11 2005
Bug Fixes
- Ensure object is removed from index when delete()d (Tim Bunce)
- clear_object_index when new relationship set up (Tim Bunce)
- Fixed bug where PK values got auto-vivified
(Tatsuhiko Miyagawa, Christopher L. Everett, Tim Bunce)
- Removed 'AS' when aliasing tables; some databases don't like that
- Properly return -1 from unchanged object updates (Kingsley Kerce)
- Fixed problems with overloaded stringification of related classes
(Tim Bunce)
- Fixed bug where Essential might contain the PK twice
Refactorings
- Split live_object_key for easy subclassing (Tim Bunce)
- Split out _as_hash() to return underlying data hash
- Optimised _mk_column_accessors (Maurice Aubrey)
- Don't hard-code relationship names (Peter Speltz)
Internals
- Changed error message when setting up has_a with incorrect column
(Drew Taylor)
Documentation
- Fixed docs for after_update trigger and update (Kingsley Kerce)
3.0.2 Sep 11 2005
Code
- No changes
Pre-Reqs
- Fixed code to explicitly need 5.6 (rather than just Makefile)
- Require 'version' for new 3 part versions
Tests
- Fixed t/01 to check mutator_name better
- Added NOT NULL to Primary in t/Blurb to avoid 0.95 regression
- Added new Test base class Class::DBI::Test::SQLite
- Changed all remaining uses of eq_set() to is_deeply()
Documentation
- Documented $obj->id() in list context (William McKee)
- Documented cascading delete for might_have (Tom Hukins)
- Documented MCFK better (plus fixed lots of typos etc) (Tom Hukins)
- Documented DBIx::ContextualFetch better
- select_val better (Dave Howorth)
- Fixed misspelling of Perrin Harkins
- Fixed documentation for the year constraint (Andy Lester)
- Fixed set_sql documentation to explain when it creates a method
- Fixed new_music documentation (Carl Johnstone)
- Fixed docs for CD columns to show 'reldate' (Mark Thomas)
- Fixed lots of other tiny doc issues
- Fixed docs for Essential (defaults to Primary, rather than All)
- Fixed docs for what gets passed to triggers (Ryan Tate)
3.0.1 Sep 11 2005
- Code is identical to 0.96
- New section added to documentation on Release Philosophy
- Replace eq_set with is_deeply in t/04 to work around Test::More bug
|
|
of Perl files to deal with the perl-5.8.7 update that moved all
pkgsrc-installed Perl files into the "vendor" directories.
|
|
These paths are now relative to PERL5_PACKLIST_DIR, which currently
defaults to ${PERL5_SITEARCH}. There is no change to the binary
packages.
|
|
|
|
|
|
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
|
|
|
|
Class::DBI provides a convenient abstraction layer to a database.
It not only provides a simple database to object mapping layer, but can
be used to implement several higher order database functions (triggers,
referential integrity, cascading delete etc.), at the application level,
rather than at the database.
This is particularly useful when using a database which doesn't support
these (such as MySQL), or when you would like your code to be portable
across multiple databases which might implement these things in
different ways.
In short, Class::DBI aims to make it simple to introduce 'best practice'
when dealing with data stored in a relational database.
|
