At 6:38 PM -0400 8/11/99, Ram Rajadhyaksha wrote:
>Well, I did change the name of the field, but it still will not display
>properly as "NOT NULL" in the table status:
>
>>mysql> ALTER TABLE tblCounties CHANGE MODT MODT TIMESTAMP NOT NULL;
>>Query OK, 88 rows affected (0.02 sec)
>>Records: 88 Duplicates: 0 Warnings: 0
>>
>>mysql> describe tblCounties;
>>+------------+---------------+------+-----+---------+----------------+
>>| Field | Type | Null | Key | Default | Extra |
>>+------------+---------------+------+-----+---------+----------------+
>>| ID | int(11) | | PRI | 0 | auto_increment |
>>| COUNTYCODE | char(3) | YES | | NULL | |
>>| COUNTY | varchar(255) | YES | | NULL | |
>>| MODT | timestamp(14) | YES | | NULL | |
>>+------------+---------------+------+-----+---------+----------------+
>>4 rows in set (0.00 sec)
>
>Unfortunately, changing the name of the field did not affect anything.
>
>Is this a problem with the driver or does Access just suck? I'd be willing
>to contribute work on the driver if it is the problem. (never touched ODBC
>stuff before though)
TIMESTAMP columns *always* display as NULL in the output of DESCRIBE
(and SHOW COLUMNS). This is somewhat confusing, yes, but the meaning
is that you can insert a NULL without an error occurring. The value
turns into the current date and time, of course.
--
Paul DuBois, paul@stripped
