| List: | MySQL++ | « Previous MessageNext Message » | |
| From: | Warren Young | Date: | February 29 2008 8:08pm |
| Subject: | Re: Strange behavior of connect() when specifying a different port | ||
| View as plain text | |||
António Santos wrote: > > I really don't know what is going on since if I use the C API directly, > everything works ok... The examples accept a port parameter. Does that work? Is there a my.cnf or similar setting somewhere forcing the port number?
| Thread | ||
|---|---|---|
| • Strange behavior of connect() when specifying a different port | António Santos | 27 Feb |
| • Re: Strange behavior of connect() when specifying a different port | Warren Young | 28 Feb |
| • Re: Strange behavior of connect() when specifying a different port | William F. Dowling | 29 Feb |
| • Re: Strange behavior of connect() when specifying a different port | António Santos | 28 Feb |
| • Re: Strange behavior of connect() when specifying a different port | Warren Young | 28 Feb |
| • Re: Strange behavior of connect() when specifying a different port | Warren Young | 28 Feb |
| • Re: Strange behavior of connect() when specifying a different port | António Santos | 29 Feb |
| • Re: Strange behavior of connect() when specifying a different port | Warren Young | 29 Feb |
| • Re: Strange behavior of connect() when specifying a different port | António Santos | 6 Mar |
| • Re: Strange behavior of connect() when specifying a different port | Warren Young | 7 Mar |