Hello Jonathan,
>> 2. engine.client_encoding - encoding for client side strings, i.e. >> string that user feeds to sqlalchemy or gets from it. Defaults to >> 'ascii', or some other encoding common to most of >> sqlalchemy users > Unnecessary to have a separate SA setting. That's what the locale module is > for; use that instead. Can you be more specific, please? I can't find anything in locale module that will help in this case. There is a sys.setdefaultencoding() function, but I actually never managed to get it work... >> 3. engine.autoload_unicode, defaults to False - parameter that tells > sqlalchemy should id >> create columns of string type or unicode type when autoloading >> tables, or perhaps some other way to hint column types when >> autoloading. > If you're not happy with what you set at the engine level, you should just > create an explicit class for that table instead of piling on the autoload > options. If I understand you correctly, you suggest explict specification of table columns. Right? But isn't autoload option exactly for avvoiding explict column specification? -- Best regards, Vasily mailto:[EMAIL PROTECTED] ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
