You were all right. I created some functions and one of them creates a connect string from parameters read from a config file. One of these is the database port. When I checked the function in the external library I saw that I didn't include it in the return. mysql://user:passw...@127.0.0.1/database
Because I use it for a few months now without problems I assumed there were no problems with it because I always used default ports. Fixed it and it works like sunshine :-) Thanks for all your input. I couldn't see the trees through the forest anymore, as we say in my country. On Mar 25, 8:29 pm, "Michael Bayer" <mike...@zzzcomputing.com> wrote: > > > Is this a known issue or should I report this as a bug? > > SQLAlchemy calls MySQLdb.connect directly with the parameters you give it, > so nothing on SQLA end. you would have to share with us the exact > parameters you pass to MySQLdb.connect, versus those you pass to > create_engine(), and the difference will be apparent. > > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
