Fernando Pérez Rodríguez

Pin Test Table example: CREATE TABLE IF NOT EXISTS `Pin_test` ( `ID` int(11) NOT NULL AUTO_INCREMENT, `CellsWithRemains` int(5) DEFAULT '0', `UnopenedSealedCell` int(5) DEFAULT '0', `colony_info_ID` int(11) NOT NULL, PRIMARY KEY (`ID`), KEY `colony_info_ID` (`colony_info_ID`), CONSTRAINT `ced_st_fk` FOREIGN KEY (`colony_info_ID`) REFERENCES `colonies` (`colony_info_ID`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Set of Database Relationship Rules (DRR) and Database Operational Rules (DOR) considered in the architecture of the generic database. Name | Name DRR1 | One apiary can have an infinite number of colonies DRR2 | One colony can fit into an infinite number of hives' elements DRR3 | One colony can be moved between apiaries in different time periods DRR4 | One hive can be moved between colonies in different time periods DOR1 | Every activity (evaluation or management) in the apiary must be registered...

This evaluation is related with colony level. The direct relationship with foreign key colony_info_ID gives information of where and when this evaluation have done. If you need create new evaluation at colony level, please see the generic code in files section for this level. Code example: CREATE TABLE IF NOT EXISTS `colonystate_queen` ( `ID` int(11) NOT NULL AUTO_INCREMENT, `Eggs` tinyint(1) DEFAULT '0', `Larvae` tinyint(1) DEFAULT '0', `Pupae` tinyint(1) DEFAULT '0', `Queen` varchar(10), `LayingWorker`...

This evaluation fields is related to colony level, so is directly link with the foreing key colony_info_ID. This store information like if a colony has Varroa, Deformed wing bee, etc. This variables ar declared as tinyint (or boolean). You can add more variables if you want, or create new evaluation field table related to colony level (see the code in files section) Code example: CREATE TABLE IF NOT EXISTS `deseases` ( `ID` int(11) NOT NULL AUTO_INCREMENT, `Varroa` tinyint(1) DEFAULT '0', `Deformed_Wing_Bee`...

The hive evaluation data is related to count, for example, items in esctructural elements. For example counter of bees, weight of honey, etc. This kind of tables are direct linked with Hive_info_ID foreing key, makig direct relationship with the chronological data associated to each evaluation. Code example: CREATE TABLE `hive_evaluation_data` ( `ID` int(11) NOT NULL AUTO_INCREMENT, `ElementID` int(1) NOT NULL, `Hive_info_ID` int(11) NOT NULL, `Frame` int(3) DEFAULT '0', `BeesFront` int(3) DEFAULT...

This evaluation fields is related to colony level, so is directly link with the foreing key colony_info_ID. This store information like if a colony has Varroa, Deformed wing bee, etc. This variables ar declared as tinyint (or boolean). You can add more variables if you want, or create new evaluation field table related to colony level (see the code in files section) CREATE TABLE IF NOT EXISTS `deseases` ( `ID` int(11) NOT NULL AUTO_INCREMENT, `Varroa` tinyint(1) DEFAULT '0', `Deformed_Wing_Bee` tinyint(1)...

This evaluation is related with colony level. The direct relationship with foreign key colony_info_ID gives information of where and when this evaluation have done. If you need create new evaluation at colony level, please see the generic code in files section for this level. -- CREATE TABLE IF NOT EXISTS `colonystate_queen` ( `ID` int(11) NOT NULL AUTO_INCREMENT, `Eggs` tinyint(1) DEFAULT '0', `Larvae` tinyint(1) DEFAULT '0', `Pupae` tinyint(1) DEFAULT '0', `Queen` varchar(10), `LayingWorker` tinyint(1)...

Data-Bee is an Open Source database scheme for chronological data storing based on apiaries system abstraction. The Data-Bee philosophy and main goal are to share the model, opening the possibility of change it or improve it. This discussion section is the windows to share the improvements or utilities.