Thanks guys for the quick replies - Its not that SQLObject isn't capable, its that our data model isn't a typical data model. We have a data broker type situation, where a centralized server distributes data to all the clients. Typically, this server will go to a database and get the information, but sometimes it will have to query an LDAP store or possibly even servers themselves (to see how much disk space is available or something). Because our data store requirements are so out there, we can't use something with a simple object to db schema mapping.
Hell, if I know the data broker team, there's a good chance they're using SQLObject for the DB stuff anyway :) I'm sorry for not clarifying this more in my first post. That said, does Matthew's advice still apply? All it would take is changes to the model.py? We know it won't be as simple as a 3 line change, but if we can isolate the framework changes to just one file (or at least one db specific package) that would make TurboGears that much more enticing. Thanks again, leo
