Ticket #601 (closed task: duplicate)
tg-admin should expose command to call create_extension_model for extensions
| Reported by: | Jeff Watkins | Owned by: | anonymous |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.1.x bugfix |
| Component: | tg-admin (non-toolbox) | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
In order to fully support turbogears extensions, tg-admin should provide a command for creating the extension's data model (calling each extensions create_extension_model method).
Currently Visit and Identity create their models during initialisation, which is causing some trouble for those who would like to more carefully control model creation (Ticket #595).
Change History
comment:1 Changed 7 years ago by kevin
- Component changed from CherryPy to TurboGears
- Milestone changed from 0.9a1 to 0.9
comment:3 Changed 7 years ago by jorge.vargas
At least for identity the approach was moving the code into the model, I don't think this should happen with Visit.
as for other modules it will be a little tricky, I'm thinking about a security problem you will have a thirdparty module going thru the same connection as your code. and yes I know TG itself is 3th party but it's a more trustable 3th party that some code from some guy from chesse shop (no offence to pipy)
comment:4 Changed 7 years ago by jorge.vargas
- Type changed from enhancement to task
- Milestone changed from 0.9 to 1.0
comment:5 Changed 7 years ago by jorge.vargas
- Component changed from TurboGears to tg-admin (non-toolbox)
- Milestone changed from 1.0 to 1.1
this should be 1.1
comment:6 Changed 6 years ago by alberto
- Milestone changed from 1.1 to __unclassified__
Batch moved into unclassified from 1.1 to properly track progress on the later
I'm bumping this from 0.9a1 because I'm not completely certain about whether we want to extend "sql create" or if a different solution might be better.