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

[Lionel B. <lio...@bo...>]

David Rees wrote:

>On 6/1/05, Michel Bouissou <mi...@bo...> wrote:
>  
>
>>Yes. I took a look at the code and can't explain either. And if I try to alter
>>the table to change/remove the defaults, MySQL accepts the command, but a
>>following "desc" shows that it is actually purely ignored... Go figure.
>>    
>>
>
>Gotta love the way MySQL tends to do that...
>
>  
>

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 |       |
+---------------+---------------+------+-----+----------------+-------+

Michel, you can force SQLgrey to create new tables from scratch and
populate them with your current data with SQLgrey 1.5.7:
- Backup your database!
- Update the 'config' table so that the stored "version" is '2'
(currently it should be '3' on your config).
- Restart with SQLgrey 1.5.7.

The 2 -> 3 upgrade process doesn't do anything fancy with the data (it
only fetches the content in the old tables and put them in new ones with
enough room for IPv6 addresses) so it should be pretty safe.
Please post "desc from_awl;" result again if it changes.

MySQL here is 4.0.24, could make a difference...

Lionel