|
From: Jorge A. B. <jor...@gm...> - 2007-09-17 11:30:33
|
Helen: Ok, it=B4s for connection. But, dont yo think could be better to define a single/standard charset and dialect for connection, use it all time, and forget about defining them at ODBC? I have SQL Server and MySQL ODBC DSN here, and none of them asks for charsets (being dialect IB/FB exclusive). Regards 2007/9/16, Helen Borrie <he...@fi...>: > > At 10:59 AM 17/09/2007, you wrote: > >Is there any reason to ask charset and dialect to user in DSN window? > > Yes, absolutely. > > >Shouldnt be obtained from the DB at connect time? > > How could it? ODBC is a *client* interface. A client has to be > *connected* to a database in order to read the database > file. Charset and dialect are connection parameters, i.e., they are > needed for the connection request. > > Helen > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > |