I start to understand how the mapper works, so I can refine my example (everything is fictional, just a textbook example)
Let's say I moreover want to manage playlists with in a table as such as PLAYLIST_TABLE ( playlist_ident * , track_ident ) now, in fact, I don't need to store any information about the track I couldn't put in the META_TABLE. So I plan to get rid of the TRACK_TABLE. Keeping : TRACKMETA_TABLE ( track_ident * , field_name * , field_content ) nevertheless I'm still interested in managing TRACKMETA_TABLE information from a dict-like class. Playing with sqlalchemy all day, I can't avoid the class pair : Track and TrackMeta (and associated pair of tables) \o/ Sorry for going round in spirals :) -- 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.
