ODBC Connect config file
Tentin Quarantino <[email protected]>
| Newsgroups | gmane.comp.python.egenix.user |
|---|---|
| Message-ID | <[email protected]> |
Hello, I recently experienced the following while using the ODBC Connect product. In my config file, there was a comment following a name-value pair. I am not necessarily experienced in ODBC conventions. However, it seems reasonable to put comments on the same line as data: [Logging] log_file = client.log [Communication] server_connections = mxODBCServerConnection [mxODBCServerConnection] # host = 192.168.1.100 # a comment host = 192.168.1.121 # a comment port = 6632 using_ssl = 0 Apparently, putting a comment after the "name = value" pair will cause the software to fail and the resulting error message could possibly mislead the programmer, IMHO. 0010 2009-06-13 12:31:26.87 [p2561] Could not open log file "<open file 'test-client.log', mode 'w' at 0x2d85c0>" - using stderr 0500 2009-06-13 12:31:26.87 [p2561] Connection to 10.10.3.252 #:6632 failed - fail-over to the next. 0010 2009-06-13 12:31:26.87 [p2561] ERROR: None of the configured mxODBC Connect Servers allow connections. I believe it would be better to have a layer of error checking between the place where the program reads the config file and where that data is delivered to the code that uses it. i.e. check & sanitize the data before using it. If error handling and messaging was slightly more helpful, then the marginal improvement would move ODBC Connect toward real world clas product status. Many thanks for the very helpful product support! Cheers! _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users