X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FManual%2FCookbook.pod;h=b4d52da48c8d562280e44d5432491aa4045f5b16;hb=51bec050485100ecaf8584325a7e9bce9d4fd6bc;hp=5524c18143357ec22b331cff456d1b873a85e6c8;hpb=7c14c3cf3b25759613e2ecef2e2b50029b555745;p=dbsrgits%2FDBIx-Class-Historic.git diff --git a/lib/DBIx/Class/Manual/Cookbook.pod b/lib/DBIx/Class/Manual/Cookbook.pod index 5524c18..b4d52da 100644 --- a/lib/DBIx/Class/Manual/Cookbook.pod +++ b/lib/DBIx/Class/Manual/Cookbook.pod @@ -367,8 +367,8 @@ That creates the following SQL: =head2 Predefined searches -You can write your own L class by inheriting from it -and defining often used searches as methods: +You can define frequently used searches as methods by subclassing +L: package My::DBIC::ResultSet::CD; use strict; @@ -415,6 +415,12 @@ supports indexes on expressions - including return values of functions - and you create an index on the return value of the function in question.) However, it can be accomplished with C when necessary. +Your approach for doing so will depend on whether you have turned +quoting on via the C and C attributes. If you +explicitly defined C and C in your +C (see L) then +you are using quoting, otherwise not. + If you do not have quoting on, simply include the function in your search specification as you would any column: