Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Re: [OT] When coders don't see eye to eye

by castaway (Parson)
on Oct 30, 2006 at 08:33 UTC ( #581229=note: print w/ replies, xml ) Need Help??

in reply to [OT] When coders don't see eye to eye

It's not "which is better" that you need to look at, but "Which better fits our needs"? As someone already pointed out for example, storing "Removed by USERNAME" has implications as at some point you may want to have localised versions of that message. You may want to link to that username in the message, and if you later change how users are linked to, you'll need to update all those.

Both your approaches have the two tables needing to be kept in sync, which means you need to do careful transaction work to make sure they don't end up disagreeing. I wouldn't use either, I'd probably have the posts table not know anything about deletions, and the removed table list post_id, deleted_by_id, date etc. SQL will quite happily create the list of all posts with/without deletions for you, you can even build the "Removed by username" message in it.

select posts_tbl.post_id, case deleted_by_id is not null then 'Removed by ' || else posts_tbl.message end as message, from posts_tbl left join removed_tbl on posts_tbl.post_id = removed_tbl.post_id left join authors as deluser on removed_tbl.deleted_by_id = +thor_id left join authors user on user.author_id = posts_tbl.author_id
.. as a rough example of how that works.


Comment on Re: [OT] When coders don't see eye to eye
Download Code

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://581229]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (6)
As of 2015-10-10 15:16 GMT
Find Nodes?
    Voting Booth?

    Does Humor Belong in Programming?

    Results (257 votes), past polls