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

[Michel B. <mi...@bo...>]

Le Mercredi 01 Juin 2005 18:17, Lionel Bouton a =E9crit :
>
> I checked the code and didn't spot any obvious mistake (no UPDATE
> involves first_seen).

Possibly an unwanted consequence of this column definition that may behav=
e=20
differently in MySQL compared to PostgreSQL ?

mysql> desc from_awl;
+---------------+--------------+------+-----+---------------------+------=
-+
| Field         | Type         | Null | Key | Default             | Extra=
 |
+---------------+--------------+------+-----+---------------------+------=
-+
| sender_name   | varchar(64)  |      | PRI |                     |      =
 |
| sender_domain | varchar(255) |      | PRI |                     |      =
 |
| src           | varchar(39)  |      | PRI |                     |      =
 |
| first_seen    | timestamp    | YES  |     | CURRENT_TIMESTAMP   |      =
 |
| last_seen     | timestamp    | YES  | MUL | 0000-00-00 00:00:00 |      =
 |
+---------------+--------------+------+-----+---------------------+------=
-+

Do you think this may cause first_seen to be automagically set to=20
CURRENT_TIMESTAMP each time a record is updated without specifying anythi=
ng=20
about first_seen     ?

--=20
Michel Bouissou <mi...@bo...> OpenPGP ID 0xDDE8AC6E