| List: | MySQL++ | « Previous MessageNext Message » | |
| From: | Warren Young | Date: | February 28 2008 9:06pm |
| Subject: | Re: Strange behavior of connect() when specifying a different port | ||
| View as plain text | |||
António Santos wrote: > > if (!conn.connect("wgwps", "127.0.0.1", "ans", "bns", 4040)) The address may be the problem. The C API recognizes special addresses like this and can interpret them oddly. Try "localhost" instead.
| 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 |