Just one more thing to consider. Sometimes we need not only a better way to specify session options before calling "connect", but also an interface for asking what session options are actually in use.
For example, when connecting to Oracle, one can specify the locale encoding for text using environment variable NLS_LANG. On Windows this can also be done via a registry key. Sometimes it's even hard to predict which setting will have the effect. For better interoperability application might ask the session what encoding is used. Here is a low-level SQL Oracle driver for Python, like a backend in SOCI. It provides backend-specific interface for retrieval of such session parameters. http://cx-oracle.sourceforge.net/html/connection.html#Connection.encoding I'm not sure that this is problem is closely related to passing parameter for a new session, though. -- View this message in context: http://soci.6940.n7.nabble.com/soci-users-RFD-how-to-specify-whether-ODBC-backend-should-prompt-the-user-tp3240p3329.html Sent from the soci-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
