Special database schemas or rules sometimes interfere with the standard ways that Kodo interacts with the database to create, delete, update, or load objects. In these situations, Kodo's custom class mapping capabilities can be critical. For example, you may have a requirement that all deletes happen via a stored procedure that does some auditing and user validation, or that loaded data should be filtered based on some application-specific authentication rules. These types of class-level data access requirements can be implemented by creating a custom class mapping. See Section 7.6.5, “Custom Class Mapping” for details about custom class mappings.