Restriction *is* on the database too, when you run "manage.py startsql" (the command that outputs the CREATE TABLEs) you can see the UNIQUE being added. But Bryan is updating his model, adding the UNIQUE after the table has been created...
On 1/17/06, Jordi Funollet <[EMAIL PROTECTED]> wrote: > > Julio Nobrega dixit: > > Afaik Django enforces uniqueness at the application level, but you > > could always add it to the database: > > Ouch. Really? So Django is assuming that we are going to work with their > database *exclusively* through Django, and doesn't protect us from doing silly > things to the data when integrating with other applications. > > This restriction should be on database, shouldn't it? > > -- > ############################## > ### Jordi Funollet > ### http://www.terraquis.net >
