Hi,
I'm trying to implement a versioning mechanism similar to this recipe:
http://www.sqlalchemy.org/trac/wiki/UsageRecipes/VersionedMap
The idea: as in the example I'd like to have (lets say) a Config of
which the data ist stored in vertical tables. The difference to the
example: I'd like to have different tables for different types
(instead of stuffing all kinds of values into one table). It should
have the same versioning mechanism.
So my tables would be:
config
config_string_assoc
string_values
config_daterange_assoc
daterange_values
...
And how I'd like the code to be:
config.data["username"] = "Joe"
config.data["duration"] = ("11.11.2009", "12.11.2009")
etc
Or maybe even better (not sure which one is easier to achieve):
config.data["username"] == {"type": "string", "value": "Joe"}
config.data["duration"] == {"type": "daterange", "value1":
"11.11.2009",
"value2": "12.11.2009"}
type, value, value1, and value2 would be column names. Does that
relate to column_mapped_collection?
I'd be thankful for any hints on which mechanisms of SQLA would help
or which classes to use.
Thanks
Tim
--
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.
