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

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

Lionel Bouton a =E9crit :
>
> MySQL really doesn't want to behave :-(
>
> If there isn't a workaround to disable this behaviour, then switching
> first_seen and last_seen would be a quick fix.

Could be the easiest way.

> I'll have to be sure about this though. Michel, what is the exact MySQL
> version you are currently running ? I'll emerge the most close from
> Portage and do some tests with it.

I'm running MySQL-4.1.11.

I have just compared on several machines on which SQLgrey has been
installed the same day last week, some running MySQL 4.0.x and others
running MySQL 4.1.x, all having installed SQLgrey 1.5.6 from scratch.

The problem clearly appears ONLY on machines using MySQL 4.1, and not on
machines running MySQL 4.0. Only machines running 4.1 show a DEFAULT
CURRENT_TIMESTAMP for first_seen.

The MySQL documentation also discusses differences in the way "timestamp"
type fields work in 4.0 in 4.1, although this doesn't look neither very
clear nor very logical to me, but I just had time to take a very quick
glimpse at the documentation...

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