sqlalchemy / sqlalchemy/alembic
add support for global table_options, others
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
Migrated issue, originally created by Michael Bayer (@zzzeek)
right now the only way to get at the Table etc. created by op directives is to use events, and that means indiscriminate targeting which could leak into other areas of the process space. There should be more options for this. also look into duplicating naming_convention across.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named; start by tracing how op directives create Table objects and how events currently target them. Compare the requested global table_options behavior with carrying naming_convention across, and define focused tests for scoped options without indiscriminate process-wide effects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlalchemy
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100