Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Interestingly added CSS3 support for the first time. Welcome to the awesome
dashing top bar.
|
|
subtemplate.
|
|
|
|
|
|
Had missed my eyes in the last run.
|
|
|
|
|
|
|
|
--HG--
extra : rebase_source : a8df73c37547e5e3e7ba413f53c0e5a7ed1012b0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
coded URLs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
generation instead of hard coded URLs.
|
|
|
|
|
|
|
|
|
|
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.
--HG--
extra : rebase_source : f02c906ecc68657d554cf3fb2da471252a4f62dd
|
|
--HG--
extra : rebase_source : 2571cb595ba7418de5fb46e4eca8e5b058708730
|
|
--HG--
extra : rebase_source : 2a3fb4c76f06c3e5cb2d29f06cfdb268a41cf9a4
|
|
|
|
should be run on every instance separately.
|
|
|
|
|
|
|
|
|
|
|