but they are not parsed because of the column id_log in which only actions with a value of 1 will show.

All other have a value of 2, I experimented a little by changing all the values to 1 in SQL and then they showed up but had no discernible action associated with them aside from the SQL value.

So this is not just a database thing it is also a way that SMF parses and displays the SQL results

Kindred:
only if it could be turned off.... I have no need or desire for that detail in logging... and with my database already pushing 3 gigs on messages alone, I don't need more crap stored in the log tables.

[Crash_Override]:
well that's just the thing all of those log entries I mentioned, just sit there in the database and take up space. They are not purged by any function in SMF (only the main ones like the topic delete/move/lock/etc . . .) unless you actually go into your SQL database and truncate that table.

BTW 3gb your lucky as most hosts have at most a 1gb total size for SQL databases.