On Wed, 2012-06-06 at 00:43 -0400, Aamir Khan wrote: > > *Database Schema: *Table structure is very straightforward and simple. > > Table name : ratings > > table structure > emailid int| userid int| value (+1/-1) > > where, > emailid - references to unique entry storing the actual emails. > userid - references to unique entry in user table. > value - +1 for upvote and -1 for downvote. > > In this case each upvote/downvote will be saved as a separate row in > database. Your suggestions?
I actually would like to ask you to think at a broader level. Could you provide us a database schema on how it would look ? You would have a user table, I assume, the tables for the archives and I would like you to consider in your design ratings but also the category and tags assigned to the emails. You can use Dia, inkscape or http://dbdsgnr.appspot.com/app (from which you can export to an image) to draw the database schema. I have given it some thoughts but I have not found yet a solution that satisfies me, so I would like you to think about it and come up with your design. Thanks, Pierre _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
