On Sat, Jun 19, 2010 at 10:12 AM, Venkatraman S <venka...@gmail.com> wrote:
> Prefer a table like follows (tblname:samples): sampleid, samplename , > sampledesc etc etc > Ok - i missed explaining why i would recommend this: In most of the applications, maintainence is a bigger pain than development. In your case, i do not think that this table would contain a billion records and even if it does, this design helps in sharding. Maintaining this system in latter case would be more of a db-admin or sys-admin job - and already there are many solutions in addition to sharding, when the size of a single table is HUGE. (when Facebook can contain the entire 32Gb profile data in the RAM, doesnt the world look small? ;) ) -V- http://twitter.com/venkasub -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
