On 23/03/2011 09:14, lars van gemerden wrote:
- I want to generate classes/tables based on metadata in another
table in the database, filled by "designers" not programmers.
Then you should be creating Tables and Mappers, not attempting to use
Declarative.
- Multiple inheritance (from the designer perspective) provides
flexibility in contracts ~ data attributes an object is sure to provide.
I don't know what this means, please explain.
- The diamond problem would complicate matters too much for
I don't know what "the diamond problem" this, please explain.
- SQLalchemy does not provide multiple inheritance (just single) out
of the box, as far as i have been able to figure out.
Did you look at Table Inheritance?
I think for your needs that Declarative is a confusing distraction.
I'd avoid it...
There are more requirements, like in the end having (persistent) objects
that still work like python classes for basic programming.
Yep, sounds like tables, model classes and mappers to bridge the two to
me...
Not all problems can be solved with a simplistix approach ;-).
The Simplistix approach has always been to find the simplest solution
that solves all the requirements. You still appear to be going in for an
extremely complex solution to a problem you don't fully understand...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" 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/sqlalchemy?hl=en.
