uh yeah definitely...create_engine takes the str or unicode so the BoundMetaData should as well...rev 2325.
On Feb 16, 2007, at 12:41 PM, Evandro Miquelito wrote: > Hello! > > First of all I would like to congratulate SQLAlchemy developers for > this amazing toolkit. I have been worked with SQLObject until I > realized how well organized, full featured and well documented > SQLAlchemy is. After that, making the decision about switching to > it was easy. > > As the subject of this message says, I'm having an issue with > unicode database paths on win32. After playing a litle bit with the > code I got the following and kinda trivial patch. I hope it helps. > > Regards. > > -- > Evandro Vale Miquelito > [EMAIL PROTECTED] > > > Index: lib/sqlalchemy/schema.py > =================================================================== > --- lib/sqlalchemy/schema.py (revision 2324) > +++ lib/sqlalchemy/schema.py (working copy) > @@ -914,7 +914,7 @@ > """builds upon MetaData to provide the capability to bind to > an Engine implementation.""" > def __init__(self, engine_or_url, name=None, **kwargs): > super(BoundMetaData, self).__init__(name, **kwargs) > - if isinstance(engine_or_url, str): > + if isinstance(engine_or_url, basestring): > self._engine = sqlalchemy.create_engine(engine_or_url, > **kwargs) > else: > self._engine = engine_or_url --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
