SiT! Bugs

View Revisions: Issue #1743 All Revisions ] Back to Issue ]
Summary 0001743: Inconsistencies in DB model
Revision 2011-12-12 17:18 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

>> USERID <<<

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `createdby` INT NULL ,
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,

TABLE `updates`
  `currentowner` tinyint(4) NOT NULL default '0',

------------

>>> USERSTATUS <<<

CREATE TABLE IF NOT EXISTS `userstatus` (
  `id` int(11) NOT NULL,

CREATE TABLE IF NOT EXISTS `tempassigns` (
  `userstatus` tinyint(4) NOT NULL default '1',

------------

>>> ROLEID <<<

CREATE TABLE IF NOT EXISTS `roles` (
`id` INT( 5 ) NOT NULL AUTO_INCREMENT ,

CREATE TABLE IF NOT EXISTS `rolepermissions` (
  `roleid` tinyint( 4 ) NOT NULL default '0',

------------

>>> PRIORITY <<<
Question: Which fields called "priority" refer to records in table priority?

CREATE TABLE IF NOT EXISTS `priority` (
  `id` int(11) NOT NULL auto_increment,

CREATE TABLE IF NOT EXISTS `servicelevels` (
  `priority` int(5) NOT NULL default '0',

CREATE TABLE IF NOT EXISTS `tasks` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `incidents` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `billing_periods` (
  `priority` INT( 4 ) NOT NULL,

CREATE TABLE IF NOT EXISTS `service` (
  `priority` smallint(6) NOT NULL default '0',

------------

>>> RESELLERID <<<

CREATE TABLE IF NOT EXISTS `resellers` (
  `id` tinyint(4) NOT NULL auto_increment,

CREATE TABLE IF NOT EXISTS `maintenance` (
  `reseller` int(11) default NULL,
Revision 2011-12-12 16:16 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

>> USERID <<<

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `createdby` INT NULL ,
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,

TABLE `updates`
  `currentowner` tinyint(4) NOT NULL default '0',

------------

>>> USERSTATUS <<<

CREATE TABLE IF NOT EXISTS `userstatus` (
  `id` int(11) NOT NULL,

CREATE TABLE IF NOT EXISTS `tempassigns` (
  `userstatus` tinyint(4) NOT NULL default '1',

------------

>>> ROLEID <<<

CREATE TABLE IF NOT EXISTS `roles` (
`id` INT( 5 ) NOT NULL AUTO_INCREMENT ,

CREATE TABLE IF NOT EXISTS `rolepermissions` (
  `roleid` tinyint( 4 ) NOT NULL default '0',

------------

>>> PRIORITY <<<
Question: Which fields called "priority" refer to records in table priority?

CREATE TABLE IF NOT EXISTS `priority` (
  `id` int(11) NOT NULL auto_increment,

CREATE TABLE IF NOT EXISTS `servicelevels` (
  `priority` int(5) NOT NULL default '0',

CREATE TABLE IF NOT EXISTS `tasks` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `incidents` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `billing_periods` (
  `priority` INT( 4 ) NOT NULL,

CREATE TABLE IF NOT EXISTS `service` (
  `priority` smallint(6) NOT NULL default '0',
Revision 2011-12-12 16:00 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

>> USERID <<<

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `createdby` INT NULL ,
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,

TABLE `updates`
  `currentowner` tinyint(4) NOT NULL default '0',

------------

>>> USERSTATUS <<<

CREATE TABLE IF NOT EXISTS `userstatus` (
  `id` int(11) NOT NULL,

CREATE TABLE IF NOT EXISTS `tempassigns` (
  `userstatus` tinyint(4) NOT NULL default '1',

------------
>>> PRIORITY <<<
Question: Which fields called "priority" refer to records in table priority?

CREATE TABLE IF NOT EXISTS `priority` (
  `id` int(11) NOT NULL auto_increment,

CREATE TABLE IF NOT EXISTS `servicelevels` (
  `priority` int(5) NOT NULL default '0',

CREATE TABLE IF NOT EXISTS `tasks` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `incidents` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `billing_periods` (
  `priority` INT( 4 ) NOT NULL,

CREATE TABLE IF NOT EXISTS `service` (
  `priority` smallint(6) NOT NULL default '0',
Revision 2011-12-12 15:29 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `createdby` INT NULL ,
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,

TABLE `updates`
  `currentowner` tinyint(4) NOT NULL default '0',

Question: Which of fields called "priority" refer to records in table priority?

CREATE TABLE IF NOT EXISTS `priority` (
  `id` int(11) NOT NULL auto_increment,

CREATE TABLE IF NOT EXISTS `servicelevels` (
  `priority` int(5) NOT NULL default '0',

CREATE TABLE IF NOT EXISTS `tasks` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `incidents` (
  `priority` tinyint(4) default NULL,

CREATE TABLE IF NOT EXISTS `billing_periods` (
  `priority` INT( 4 ) NOT NULL,

CREATE TABLE IF NOT EXISTS `service` (
  `priority` smallint(6) NOT NULL default '0',
Revision 2011-12-12 12:59 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `createdby` INT NULL ,
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,

TABLE `updates`
  `currentowner` tinyint(4) NOT NULL default '0',

-------------
Question: Refers field respondentid in table feedbackresults to contacts(id)?
Then we have wrong datatype there:

CREATE TABLE IF NOT EXISTS `feedbackresults` (
  `respondentid` int(5) NOT NULL default '0',

CREATE TABLE IF NOT EXISTS `contacts` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
-------------
Revision 2011-12-12 12:40 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `createdby` INT NULL ,
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,

TABLE `updates`
  `currentowner` tinyint(4) NOT NULL default '0',
Revision 2011-12-08 16:44 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,

TABLE `updates`
  `currentowner` tinyint(4) NOT NULL default '0',
Revision 2011-12-08 13:03 by dipohl
Description I review the DB schema in development version 3.90 and am finding some issues with incompatible datatypes. The table definitions need correction.

Table `users` (
  `id` smallint(6) NOT NULL auto_increment,

Foreign keys refering to users.id:

Table `files`
  `userid` int(11) NOT NULL default '0',

Table `escalationpaths`
  `modifiedby` INT NULL ,

Table `emailsig`
  `modifiedby` INT NULL ,


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker