If this parameter is omitted, this method will refuse to delete all rows from the table and a fatal error will occur. Arbitrarily nested boolean logic is supported.įor the complete list of valid parameter names and values, see the documentation for the query parameter of the build_select function in the Rose::DB::Object::QueryBuilder module. These pairs are used to formulate the "where" clause of the SQL query that is used to delete the rows from the table. The query parameters, passed as a reference to an array of name/value pairs. Defaults to the value returned by the object_class class method. This parameter is required a fatal error will occur if it is omitted. The name of the Rose::DB::Object-derived class that fronts the table from which rows are to be deleted. If omitted, the default value is determined by the dbi_prepare_cached class method. If true, then DBI's prepare_cached method will be used (instead of the prepare method) when preparing the SQL statement that will delete the objects. If omitted, one will be created by calling the init_db method of the object_class. db DBĪ Rose::DB-derived object used to access the database. If both the all and the where parameters are passed, a fatal error will occur. If set to a true value, this parameter indicates an explicit request to delete all rows from the table. If the first argument is a reference to a hash or array, it is converted to a reference to an array (if necessary) and taken as the value of the where parameter. Returns the number of rows deleted, or undef if there was an error. delete_objects ĭelete rows from a table fronted by a Rose::DB::Object-derived class based on PARAMS, where PARAMS are name/value pairs. Get or set the default number of items per page, as returned by the get_objects method when used with the page and/or per_page parameters. If this parameter is true, the feature will be used when possible, by default. Not all databases support this syntax, and not all queries can use it even in supported databases. Get or set a boolean value that determines whether or not this class will consider using nested JOIN syntax when fetching related objects. The default list is objects, iterator, count, delete, and update. Get or set the default list of method types used by the make_manager_methods method. Get or set a boolean value that determines whether or not this class will consider using a sub-query to express limit/ offset constraints when fetching sub-objects related through one of the ".-to-many" relationship types. Get or set a boolean value that indicates whether or not this class will use DBI's prepare_cached method by default (instead of the prepare method) when preparing SQL queries. A very minimal example is shown in the synopsis above. Subclasses are expected to create syntactically pleasing wrappers for Rose::DB::Object::Manager class methods, either manually or with the make_manager_methods method. Each row in the table(s) queried is converted into the equivalent Rose::DB::Object-derived object.Ĭlass methods are provided for fetching objects all at once, one at a time through the use of an iterator, or just getting the object count. Rose::DB::Object::Manager is a base class for classes that select rows from tables fronted by Rose::DB::Object-derived classes. # Given the following Rose::DB::Object-derived classes. Rose::DB::Object::Manager - Fetch multiple Rose::DB::Object-derived objects from the database using complex queries.
0 kommentar(er)
