Skip to main content ↑ ↓
Stop naming every table log_* Started by Joshua Dickerson · · Read 4224 times 0 Members and 2 Guests are viewing this topic. previous topic - next topic

Stop naming every table log_*

I know it's completely pedantic. I just noticed how many log tables there are haha

log_comments: they are comments for warning. So, "warning_comments"
log_group_requests: "group_requests"
log_likes: "likes" or "message_likes"
log_member_notices: "member_notices"
log_mentions: mentions
log_online: online_users
log_polls: poll_votes

There's a lot more but the point is there. Everything can be a log if you look at it like it but if it is more than tracking a change, it isn't. A log never gets updated. You can truncate it but the point should be to only insert in to it. Objects aren't changes, they are objects.

Not expecting changes (unless you want to haha) though.

Re: Stop naming every table log_*

Reply #1 –

I think we need a new table called log_log where we log all we change in the other log tables.  ;)

Re: Stop naming every table log_*

Reply #2 –

What's wrong? I'd prefer it that way. Easy to find log at log_*.

Re: Stop naming every table log_*

Reply #3 –

a) they aren't logs. They are tables containing objects
b) if you remove log_* you can find it even easier because they'll be ordered alphabetically
 

Re: Stop naming every table log_*

Reply #4 –

Quote from: Jorin – I think we need a new table called log_log where we log all we change in the other log tables.  ;)
There aren't enough trees for that many logs :D
LiveGallery - Simple gallery addon for ElkArte

Re: Stop naming every table log_*

Reply #5 –

prust[1]
1 which means something like rofl↵

Re: Stop naming every table log_*

Reply #6 –

Quote from: Jorin – I think we need a new table called log_log where we log all we change in the other log tables.  ;)
~ SimplePortal Support Team ~