Hi Peter, Peter Czanik <cza...@balabit.hu> was heard to say:
> With PostgreSQL if the port is not specified, libdbi tries to connect to > port 0 (zero). It works fine, once a port is specified. > I was told, that in syslog-ng all databases are treated equal, so it's > something in libdbi port handling. Not necessarily. libdbi should not fiddle with port settings at all. The drivers do not supply any default setting either if the calling application does not explicitly set the port. It might actually be a matter of how the client libraries deal with a missing port. I didn't check the docs, but MySQL, being a bit more relaxed, may very well use a compile-time default in this case, whereas the PostgreSQL lib might rather act according to "garbage in, garbage out". In order to make the drivers more consistent, we might of course supply a default port for those drivers that would otherwise fail. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ libdbi-devel mailing list libdbi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-devel
