#1146: sqlalchemy + sqlite autoload doesn't work in 1.0b1
----------------------------------------------+-----------------------------
Reporter: kkinder | Owner: anonymous
Type: defect | Status: new
Priority: low | Milestone: 1.0
Component: SQLAlchemy | Version: 1.0b1
Severity: minor | Resolution:
Keywords: sqlalchemy reflecttable autoload |
----------------------------------------------+-----------------------------
Comment (by catherinedevlin):
My guess would be that kkinder doesn't intend to create tables on the fly,
merely wants TG to work with the tables that already exist in the database
- which will nearly always be the case for work centered on existing
databases. autoload=True is easier to code than hand-typing column
specifications, and avoids errors, so it's a legitimate need;
("Legitimate" = "I had the problem, too")
After lots of websearching, I learned that calling
turbogears.database.bind_meta_data() in the model.py file, immediately
after imporing turbogears.database, fixes the problem.
So I wouldn't call it a bug or a defect, but something that documentation
possibly should highlight, since the quickstart-generated model.py doesn't
contain or hint at a bind_meta_data() call.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/1146>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en
-~----------~----~----~----~------~----~------~--~---
