GNU Info

Info Node: (mysql.info)MyODBC connect parameters

(mysql.info)MyODBC connect parameters


Next: ODBC Problems Prev: ODBC administrator Up: ODBC
Enter node , (file) or (file)node

Connect parameters for MyODBC
-----------------------------

One can specify the following parameters for *MyODBC* on the
`[Servername]' section of an `ODBC.INI' file or through  the
`InConnectionString' argument in the `SQLDriverConnect()' call.

*Parameter*    *Default       *Comment*
               value*         
user           ODBC (on       The username used to connect to MySQL.
               Windows)       
server         localhost      The hostname of the MySQL server.
database                      The default database
option         0              A integer by which you can specify how
                              *MyODBC* should work. See below.
port           3306           The TCP/IP port to use if `server' is not
                              `localhost'.
stmt                          A statement that will be executed when
                              connection to `MySQL'.
password                      The password for the `server' `user'
                              combination.
socket                        The socket or Windows pipe to connect to.

The option argument is used to tell *MyODBC* that the client isn't 100%
ODBC compliant. On Windows, one normally sets the option flag by
toggling the different options on the connection screen but one can also
set this in the opton argument. The following options are listed in the
same order as they appear in the *MyODBC* connect screen:

*Bit*   *Meaning*
1       The client can't handle that *MyODBC* returns the real width of
        a column.
2       The client can't handle that MySQL returns the true value of
        affected rows.  If this flag is set then MySQL returns 'found
        rows' instead.  One must have MySQL 3.21.14 or newer to get this
        to work.
4       Make a debug log in c:\myodbc.log.  This is the same as putting
        `MYSQL_DEBUG=d:t:O,c::\myodbc.log' in `AUTOEXEC.BAT'
8       Don't set any packet limit for results and parameters.
16      Don't prompt for questions even if driver would like to prompt
32      Simulate a ODBC 1.0 driver in some context.
64      Ignore use of database name in 'database.table.column'.
128     Force use of ODBC manager cursors (experimental).
256     Disable the use of extended fetch (experimental)
512     Pad CHAR fields to full column length.
1024    SQLDescribeCol() will return fully qualifed column names
2048    Use the compressed server/client protocol
4096    Tell server to ignore space after function name and before `'(''
        (needed by PowerBuilder).  This will make all function names
        keywords!
8192    Connect with named pipes to a `mysqld' server running on NT.
16384   Change LONGLONG columns to INT columns (Some applications can't
        handle LONGLONG).
32768   Return 'user' as Table_qualifier and Table_owner from SQLTables
        (experimental)
65536   Read parameters from the `client' and `odbc' groups from `my.cnf'
131072  Add some extra safety checks (should not bee needed but...)

If you want to have many options, you should add the above flags!  For
example setting option to 12 (4+8) gives you debugging without package
limits!

The default `MYODBC.DLL' is compiled for optimal performance.  If you
want to to debug *MyODBC* (for example to enable tracing), you should
instead use `MYODBCD.DLL'.  To install this file, copy `MYODBCD.DLL'
over the installed `MYODBC.DLL' file.


automatically generated by info2www version 1.2.2.9