Decided to scratch my own itch by adding the config option: identity.soprovider.model.create=False Basically my problems is I write my own SQL CREATE TABLE for a number of reasons but I couldn't seem to get TG to stop trying to create the table. Not sure if this is a SQLObject bug with Postgresql or if it is something wrong with the identity framework. In poking around the code I couldn't find a bug in the identity framework. So I added a config option and slaped an if condition in the identity/soprovider.py.
I was wondering if anyone else had a better idea on how to opt out of create table. Maybe a class level decorator on the soprovider subclass (Currently to overide the defualt soprovider you subclass SQLObject but maybe some extra magic in the custom subclass)? Thoughts? Thanks, Lateef --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
