On May 25, 2007, at 3:12 PM, Philip Jenvey wrote:
>> - nice to have: allow support for *any* keyword under >> sqlalchemy.XXXXX to be propigated from the .ini file to create_engine >> (), not just 'uri' and 'echo'. have awareness of the well known >> kwargs so that types can be changed from strings to ints/booleans as >> needed. >> > > How would one easily setup non int/bool/str options to pass to > create_engine? Like import pyodbc; module=pyodbc, or poolclass=Pool > ()? If we want to maintain the default > pylons.database.session_context, you need to intercept the keyword > arguments passed along to create_engine with python code. Maybe with > a setuptools entry point? the non-primitive types of arguments to create_engine() i think need to be supported by an API call. like database.setup_engine (config_key, **kwargs) or something. that will place an appropriate engine in the get_engines() dict (or just the arguments somewhere that will be used in a subsequent create_engine() call). python is great as a configurational language so i dont think the .ini file should have to be where *everything* goes. not sure what you mean by the setuptools entry point part, though. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
