zyrolasting Posted December 11, 2009 Share Posted December 11, 2009 I painted myself in a corner by jumping the gun with a comments section. It works, but my database is horrible. I only realized this after additional research. I have a blog that is categorized into multiple topics which can then be broken down into the specific articles. Since I want to have the public be able to comment on any one of the articles, I can't imagine any possible table or combination thereof that doesn't introduce duplicate entries. I only ask the user to put in a name (It's a junk name that only appears on their posted comment, they can leave it blank to be anonymous) for referencing any troublesome posts and the comment itself. I'm having trouble picturing a way to store the data that isn't horrendously redundant. I hate making a "any suggestions?" post, but I'm pretty clueless on this. Link to comment https://forums.phpfreaks.com/topic/184822-database-for-public-comments-section/ Share on other sites More sharing options...
fenway Posted December 14, 2009 Share Posted December 14, 2009 What's your definition of a duplicate? Link to comment https://forums.phpfreaks.com/topic/184822-database-for-public-comments-section/#findComment-977300 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.