Just tried it with Postgres and now import_from_csv_file() is throwing
an exception with message "duplicate key value violates unique
constraint "region_subdomain_key", so I guess this is a sqlite
specific thing.
On Mar 28, 5:33 pm, Brian Will <brian.thomas.w...@gmail.com> wrote:
> I should also make clear that I'm talking about
> db.export_to_csv_file() and db.import_from_csv_file()
>
> On Mar 28, 5:27 pm, Brian Will <brian.thomas.w...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I should add that I'm seeing this with SQLite. Haven't tried it with
> > Postgres yet.
>
> > On Mar 28, 5:25 pm, Brian Will <brian.thomas.w...@gmail.com> wrote:
>
> > > I have this table:
>
> > > db.define_table('region',
> > > Field('name'),
> > > Field('longname'),
> > > Field('subdomain', unique=True),
> > > Field('status_', 'reference region_status')
> > > )
>
> > > The unique constraint is preventing me in the appadmin from adding
> > > regions with the same subdomain, as intended. However, in playing
> > > around, I exported my whole database and then reimported, upon which I
> > > ended up with duplicate fields as if the unique constraint gets
> > > ignored for the import. Is this the intended behavior? What I'd like
> > > is for the duplicates to not get imported silently.
