Sat, 15 Jan 2011 03:59:00 +0530 Make changes to the import styles, ids used and use reverse function for URL generation instead of hard coded URLs.
Madhusudan.C.S <madhusudancs@gmail.com> [Sat, 15 Jan 2011 03:59:00 +0530] rev 408
Make changes to the import styles, ids used and use reverse function for URL generation instead of hard coded URLs.
Sat, 15 Jan 2011 03:58:06 +0530 Add name for each URL definition.
Madhusudan.C.S <madhusudancs@gmail.com> [Sat, 15 Jan 2011 03:58:06 +0530] rev 407
Add name for each URL definition.
Sat, 15 Jan 2011 03:57:25 +0530 Removed utils file whose only function is not required anymore.
Madhusudan.C.S <madhusudancs@gmail.com> [Sat, 15 Jan 2011 03:57:25 +0530] rev 406
Removed utils file whose only function is not required anymore.
Sat, 15 Jan 2011 01:19:48 +0530 Add a fixture to maintain the Sites framework data settings.
Madhusudan.C.S <madhusudancs@gmail.com> [Sat, 15 Jan 2011 01:19:48 +0530] rev 405
Add a fixture to maintain the Sites framework data settings.
Sat, 15 Jan 2011 01:16:17 +0530 Change the admin media prefix to suit the server settings.
Madhusudan.C.S <madhusudancs@gmail.com> [Sat, 15 Jan 2011 01:16:17 +0530] rev 404
Change the admin media prefix to suit the server settings.
Sat, 15 Jan 2011 00:41:50 +0530 Remove uniqkey field from every model.
Madhusudan.C.S <madhusudancs@gmail.com> [Sat, 15 Jan 2011 00:41:50 +0530] rev 403
Remove uniqkey field from every model. This field is redundant data. Every Django database model has a built-in id which is unique for that database entity. So this field becomes redundant. In addition this field is not even a primary key. So I am not sure what it is trying to achieve. It is also agains the schema design principles. Normalization level 2 is lost by having redundant data. The way uniqkey is generated using random is also awkward.
(0) -300 -100 -30 -10 -6 +6 +10 +30 +100 tip