Mr.Massimo, Thank you for your response.And it is not only the case of unique=true constraing, but also other constraints like is_not_empty. The db is not enforcing these constraints if they are not declared at the first shot. But what shall be done if i wish to enforce theses? shall i drop the table and recreate them? Kindly do reply because I need to add a few constraints after table creation.
On 5 May 2012 09:33, Massimo Di Pierro <[email protected]> wrote: > Validators are not applied to CSV import. The unique=True may be ignored > if you are suing sqlite, unless you added it when you first defined the > table. If you added unique=True later it is ignored. > > > On Friday, 4 May 2012 22:40:12 UTC-5, rahulserver wrote: >> >> I am importing data from a csv file and the field declaration is >> as:Field('Account',requires=**IS_NOT_EMPTY(),unique=True). But no >> exception is thrown when duplicate values for the field is imported! In >> one of the posts, I have read that it is an sqllite specific issue which I >> am using for backend How to get round it? >> >
