It's not intuitive and won't be needed in 99.9% of the use cases. For
single resources that may be overbooked, the resource should be created
with a RESPONSETYPE_ALWAYS_EXCEPT responseType instead.
public function getResource($id)
{
$query = 'SELECT resource_id, resource_name, resource_calendar, resource_category, resource_description, resource_response_type, resource_type, resource_members FROM kronolith_resources WHERE resource_id = ?';
-
$results = $this->_db->getRow($query, array($id), DB_FETCHMODE_ASSOC);
if ($results instanceof PEAR_Error) {
throw new Horde_Exception($results->getMessage());
}
}
- return ($conflicts < $this->get('max_reservations'));
+ return true;
}
/**
resource_name VARCHAR(255),
resource_calendar VARCHAR(255),
resource_description TEXT,
- resource_category VARCHAR(255),
+ resource_category VARCHAR(255) DEFAULT '',
resource_response_type INT DEFAULT 0,
- resource_max_reservations INT DEFAULT 1,
PRIMARY KEY (resource_id)
);