Re: [Sqlgrey-users] Memory leak in 1.5.x

[Who K. <qui...@me...>]

Lionel Bouton wrote:

>MySQL may change its behaviour from versions to versions, anyway, it
>doesn't seem to like 'NOT NULL' for timestamps... :
>
>Here's from_awl freshly created with SQLgrey 1.5.7 :
>
>+---------------+---------------+------+-----+----------------+-------+
>| Field         | Type          | Null | Key | Default        | Extra |
>+---------------+---------------+------+-----+----------------+-------+
>| sender_name   | varchar(64)   |      | PRI |                |       |
>| sender_domain | varchar(255)  |      | PRI |                |       |
>| src           | varchar(39)   |      | PRI |                |       |
>| first_seen    | timestamp(14) | YES  |     | NULL           |       |
>| last_seen     | timestamp(14) | YES  | MUL | 00000000000000 |       |
>+---------------+---------------+------+-----+----------------+-------+
>  
>
As I understand MySQL behavior the first field of type 'timestamp' is 
automatically updated updated to reflect the time of the last update to 
any field in the record.