On Sep 20, 2007, at 12:49 PM, jason kirtland wrote:
Rick Morrison wrote:
This is Python, after all, and it would be trivial to simply put
whatever attribute you want on a Table, Column or any SA object.
SA would just need to stay out of the way and agree not to use a
certain
attribute
Am Mittwoch, 19. September 2007 23:44 schrieb Paul Johnston:
Hi,
For my documentation, it is very handy to gather the table definitions
directly from my SQLAlchemy-based python code - that's relatively easy, I
This would be useful for me too, and it would be good to have hooks to
store
This is Python, after all, and it would be trivial to simply put whatever
attribute you want on a Table, Column or any SA object.
SA would just need to stay out of the way and agree not to use a certain
attribute like description or userdata, or whatever.
Rick Morrison wrote:
This is Python, after all, and it would be trivial to simply put
whatever attribute you want on a Table, Column or any SA object.
SA would just need to stay out of the way and agree not to use a certain
attribute like description or userdata, or whatever.
There is a
Hi,
For my documentation, it is very handy to gather the table definitions
directly from my SQLAlchemy-based python code - that's relatively easy, I
This would be useful for me too, and it would be good to have hooks to
store arbitrary information. I'd be using this as hints for a form
suggestions:
on the descriptions... maybe right now u can inherit Columns and
Tables and whatever by your own classes adding the .descriptions
passing all else down.
on the table-gathering, instead of python-parsing, u could just use
the metadata and walk it - it will have all your tables,
