update) that operate on a single identifer. The provided identifier will be used
to find that particular object and add it to the request's store ofobjects.
-Please see L<Catalyst::Controller::DBIC::API::Context> for more details on the
-stored objects.
+Please see L<Catalyst::Controller::DBIC::API::Request::Context> for more
+details on the stored objects.
=cut
perform an update. As a special case, a single hash sent will be coerced into
an array.
-Please see L<Catalyst::Controller::DBIC::API::Context> for more details on the
-stored objects.
+Please see L<Catalyst::Controller::DBIC::API::Request::Context> for more
+details on the stored objects.
=cut
For more information, please see L<Data::DPath::Validator> and more specifically
L<Catalyst::Controller::DBIC::API::Validator>.
-Since 2.00100:
+Since 2.001:
Transactions are used. The stash is put aside in favor of roles applied to the
request object with additional accessors.
Error handling is now much more consistent with most errors immediately detaching.
The internals are much easier to read and understand with lots more documentation.
+Since 2.006:
+The SQL::Abstract -and, -not and -or operators are supported.
+
=cut
1;