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

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

Le Mercredi 01 Juin 2005 18:17, Lionel Bouton a =E9crit :
> >
> >SQLgrey 1.5.6 + MySQL: In both AWLs, everytime last_seen is updated,
> >first_seen is updated as well, where it should not.
>
> This one obviously got through though :-)
>
> I checked the code and didn't spot any obvious mistake (no UPDATE
> involves first_seen).
>
> *But* there was a bug in the database migration code from version 2 to =
3
> in 1.5.5 IIRC : it resets the first_seen values to last_seen (drag and
> drop of code from the earlier migration where first_seen didn't exit
> yet). It is solved in 1.5.6 IIRC.

Weird enough. I have the positive certitude that the first_seen column ge=
ts=20
updated everytime the last_seen column is, on my system.

An example that is clear enouch about this ;-) :

| sqlgrey-users-admin | lists.sourceforge.net | 66.35.250 | 2005-06-01=20
18:29:00 | 2005-06-01 18:29:00 |

Cheers.

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