CaseSTUDIO 2.3 - CharonWare
ERD
Well, if the version table is been used somewhere, I have not seen it over
the years.
About the version numbering as comments. I would like to move that topic
when we killed all relevant bugs out and place a (c) setting in each
file. We have to do it,
Rough cut of ERD shows only 2 relationships.
The code does not respect the relationships however.
table care_user_roles Primary Key 'id' is an INT
Foreign Key 'user_role' in table care_users is a Tiny INT
If the numebr of anticipated roles is going to be 256 then a TinyINT would
suffice.
Made it both INT(4)
ALTER TABLE `care_users` CHANGE `user_role` `user_role` INT(4) DEFAULT '0' NOT
NULL;
ALTER TABLE `care_user_roles` CHANGE `id` `id` INT(4) NOT NULL AUTO_INCREMENT;
ALTER TABLE `care2x`.`care_yellow_paper` DROP KEY `nr`;
SVN 6783 fixed.
FK relationships avoided as we need
Attached is Part 2 of the ERD.
All the 24 care_type_* tables can be strung together to form one table.
They are listed now
- Ap.Muthu
--
Start uncovering the many advantages of virtual appliances
and start using
4 matches
Mail list logo
