Closed sqlalchemy-bot closed 16 years ago
Michael Bayer (zzzeek) wrote:
note added in 8fee8e963de1fe050c79419dc2b176e8135ca448 and is up on the site.
Changes by Michael Bayer (zzzeek): removed "0.4.xx" milestone
Changes by Michael Bayer (zzzeek): set state to "resolved"
Issue created by Anonymous
Previously in version 0.3 you could do,
and the table would get bound to the default_metadata.
It appears that 0.4 has removed the default_metadata and you now MUST specify a metadata. This is not documented in the SQL migration guide and you get this cryptic error,