Hi guys ans girls, I just ran into this relatively weird behaviour while trying to implement a specific setup in which the a2b needs to be connected to a second mysql instance using port that is different than the default one.
After tinkering a little, I just found out that the "port" parameter in a2billing.conf is totally irrelevant. It just seems to connect to my default instance no matter what I set in the file.
Could it be that someone has, while implementing the ADOdb, neglected to implement the port setting, or perhaps the driver does not use TCP at all? So far I did not give it a serious examination, but since during my GREPing of the a2billing source I haven't found any DSN definitions that mention the port, it seems that the port setting is really completely ignored
cheers, George
|