great! thanks
On Monday, June 17, 2013 9:39:25 AM UTC-7, Michael Bayer wrote:
>
>
> On Jun 15, 2013, at 4:32 PM, Rj Ewing <ewin...@gmail.com <javascript:>>
> wrote:
>
> > I am trying to do a migration and am running into a problem where my
> unique constraints are being delete with sqlite, but works fine with
> postgres.
> >
> > It seems that unique constraints are not present in the table, even
> before the migration.
> >
> > Ex.
> >
> > engine = create_engine("sqlite:///my.db")
> > Session = sessionmaker(bind=engine)
> > s = Session()
> > metadata = MetaData(s.bind)
> > t = Table('core__users', metadata, autoload=True,
> autoload_with=metadata.bind)
> >
> > t.constraints shows the pk constraint, but not the unique constraints.
> >
> > Is this a limitation with sqlite? Or am I doing something wrong?
> >
> > Any help is appreciated.
>
> unique constraints are not currently reflected. This feature was just
> added in master and is currently set for release in 0.9.0.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/groups/opt_out.
