- AUTHOR - Hilmar Lapp
Bio::DB::DBD - DESCRIPTION of Interface
Give standard usage here
Describe the interface here
User feedback is an integral part of the evolution of this and other Bioperl modules. Send your comments and suggestions preferably to the Bioperl mailing list. Your participation is much appreciated.
firstname.lastname@example.org - General discussion http://bioperl.org/wiki/Mailing_lists - About the mailing lists
Please direct usage questions or support issues to the mailing list:
rather than to the module maintainer directly. Many experienced and reponsive experts will be able look at the problem and quickly address it. Please include a thorough description of the problem with code and data examples if at all possible.
Report bugs to the Bioperl bug tracking system to help us keep track of the bugs and their resolution. Bug reports can be submitted via the web:
Email hlapp at gmx.net
Describe contact details here
Additional contributors names and emails here
The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _
Title : prepare_delete_sth Usage : Function: Creates a prepared statement with one placeholder variable suitable to delete one row from the respective table the given class maps to. The method may throw an exception, or the database handle methods involved may throw an exception. Example : Returns : A DBI statement handle for a prepared statement with one placeholder Args : The database handle to use for preparing the statement. The class of which a corresponding entry shall be deleted. Optionally, additional (named) arguments.
Title : cascade_delete Usage : Function: Removes all persistent objects dependent from the given persistent object from the database (foreign key integrity). The method may throw an exception, or the database calls involved may throw an exception. If the RDBMS supports cascading deletes, and the schema definition enabled FK constraints with cascading deletes, then the implementation won''t need to do anything. Example : Returns : TRUE on success, and FALSE otherwise Args : The DBContextI implementing object for the database. The object for which the dependent rows shall be deleted. Optionally, additional (named) arguments.