List:General Discussion« Previous MessageNext Message »
From:Steven Gearhart Date:March 22 2002 11:23pm
Subject:MySQL oddity
View as plain text  
Below is a table declaration in a database I just created. The oddity is the
2 fields, CL_FIRST_TS and CL_LAST_TS, are automatically marked as "Required"
in the table's "Validity Checks" listing. This means that I have to add a
value to both of them each time I insert a new record. They are involved in
a legacy issue by old input devices or I would remove them.

Nothing I do will change this behavior. Can anybody please explain to me why
they are the only ones in the whole database to do this? The database
consists of 90 tables with this one being number 9.

I have tried this under MySQL v3.23 and v4.01 and get the same results.

DROP TABLE IF EXISTS char_limits;
CREATE TABLE CHAR_LIMITS (
	CHAR_ID INTEGER NOT NULL,
	ENG_HIGH DOUBLE PRECISION,
	NOMINAL DOUBLE PRECISION,
	ENG_LOW DOUBLE PRECISION,
	CL_UPPER DOUBLE PRECISION,
	CL_CENTER DOUBLE PRECISION,
	CL_LOWER DOUBLE PRECISION,
	SCL_UPPER DOUBLE PRECISION,
	SCL_CENTER DOUBLE PRECISION,
	SCL_LOWER DOUBLE PRECISION,
	CL_CALC_METHOD VARCHAR(32),
	CL_FIRST_SG_TS TIMESTAMP NULL,
	CL_LAST_SG_TS TIMESTAMP NULL,
	REAS_HIGH DOUBLE PRECISION,
	REAS_LOW DOUBLE PRECISION,
	LIMITS_TS TIMESTAMP NOT NULL,
	TOTAL_LIMIT DOUBLE PRECISION,
	TOTAL_LIMIT_TYPE VARCHAR(16),
	CL_CALC_SG_SIZE INTEGER,
	CAUTION_PERCENT SMALLINT,
	CAUTION_TYPE VARCHAR(16),
	RANGE_UPPER DOUBLE PRECISION,
	RANGE_CENTER DOUBLE PRECISION,
	RANGE_LOWER DOUBLE PRECISION,
	SIGMA_UPPER DOUBLE PRECISION,
	SIGMA_CENTER DOUBLE PRECISION,
	SIGMA_LOWER DOUBLE PRECISION,
	ACC_DEFECT_PERCENT DOUBLE PRECISION,
	ACC_CONFID_PERCENT DOUBLE PRECISION,
    PRIMARY KEY (CHAR_ID));

CREATE UNIQUE INDEX CHARLIMITS_PK ON CHAR_LIMITS(
	CHAR_ID);






/*****************/
Steven Gearhart
Gearhart, Inc.
Phone/Fax: 770.466.2898
Email: sgearhart@stripped

Thread
MySQL odditySteven Gearhart23 Mar