Re: [Quickfix-developers] ODBC LOG and STORE - QuickFix 1.13.2
Brought to you by:
orenmnero
Menu
▾
▴
Re: [Quickfix-developers] ODBC LOG and STORE - QuickFix 1.13.2
|
From: <or...@qu...> - 2010-03-25 16:43:21
|
Yeah but that's not the full connect string. QuickFIX needs to generate a connect string that also has your logon and password which gets appended to the connect string you provide. So what I'm trying to find out is if the two strings are the same just before they are passed to the ODBC library, or if there is something subtly different. If the old driver worked before, I don't see why it wouldn't now. We didn't make any fundamental changes that require a newer driver as far as I can tell. But you can certainly try. It also might help to see if there are any logs generated by your database which might provide some clues. --oren > -------- Original Message -------- > Subject: Re: [Quickfix-developers] ODBC LOG and STORE - QuickFix 1.13.2 > From: AS...@bo... > Date: Thu, March 25, 2010 11:13 am > To: or...@qu... > Cc: qui...@li... > > > I can see the value when running in debug Mode : in Both version this is > the same value for the connect string : > the one entered in the cfg File : "Dsn=QuickFix;DATABASE=quickfix;" > > Could it the problem , because of the version of the Driver for ODBC SQL > Native Client, that I used ? (SQL Native Client , V 2005.90.1399) ? > should I try to update the driver ? > > - I have compiled First QuickFix Lib in release or debug Mode with the > project under Visual Studio 2008 > - then used in my Visual Studio 2008 application. > > Alain SY > Bourse Direct > Service Informatique - Developpement > Tel : (00-33-0) 1-56-43-82-34 > > > > oren@quickfixengi > ne.org > A > 25/03/2010 16:49 AS...@bo... > cc > qui...@li...urcefor > ge.net > Objet > Re: [Quickfix-developers] ODBC LOG > and STORE - QuickFix 1.13.2 > > > > > > > > > > > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > Possibly there is a problem with how the connection string is being > generated in your case. I notice some difference in the code here. Can > you modify the OdbcConnection.h files to print out what connection > string you are generating when using 1.12.4 vs 1.13.2? > > The connection string is created in the connect() method. You can add a > printout after the string is created. > > --oren > > > -------- Original Message -------- > > Subject: Re: [Quickfix-developers] ODBC LOG and STORE - QuickFix > > 1.13.2 > > From: AS...@bo... > > Date: Thu, March 25, 2010 9:34 am > > To: or...@qu... > > Cc: qui...@li... > > > > > > Hi All, > > - I was using QuickFix 1.12.4 and the ODBC Log and Store to connect and > > write messages in a MS SQL Server Database > > after some trouble with the connectring I could connect ( I finally use > > connect string : > OdbcStoreConnectionString=Dsn=QuickFix;DATABASE=quickfix; > > ) > > > > - I want to use last QuickFix Version : 1.13.2 : but cannot connect to > the > > same database ! > > My C++ project fail in : OdbcLog.h > > OdbcLog::OdbcLog > > ( const std::string& user, const std::string& password, > > const std::string& connectionString ) > > : m_pSessionID( 0 ) > > { > > init(); > > m_pConnection = new OdbcConnection( user, password, connectionString ); > > ==> Access Violation > > } > > > > (Embedded image moved to file: pic26500.jpg) > > > > > > Is there a pb or any changes with ODBC in QuickFix 1.13.2 ? > > Can someone give me an advice !!! please. > > > > Alain SY > > Bourse Direct > > Service Informatique - Developpement > > Tel : (00-33-0) 1-56-43-82-34 > > > > > > > > > oren@quickfixengi > > > ne.org > > > > A > > 19/02/2010 20:05 AS...@bo... > > > > cc > > > qui...@li...urcefor > > ge.net > > > > Objet > > Re: [Quickfix-developers] Logging > > > Incoming Messages in Database ODBC > > > > > > > > > > > > > > > > > > > > > > > > > > > > > QuickFIX Documentation: > > http://www.quickfixengine.org/quickfix/doc/html/index.html > > QuickFIX Support: http://www.quickfixengine.org/services.html > > > > You are probably using the OdbcMessageStore. A MessageStore is required > > for QuickFIX, and is not there for logging. It is there to keep > > messages in case they ever need to be reset. It is not good for logging > > because as you have noticed, only outgoing messages ever need to be > > resent, hence no incoming messages. Also, it is volatile. If you > > decide to reset the session, those messages will be blown away. > > > > Instead, you should lookg at the OdbcLog/OdbcLogFactory. This is an > > optional object which can be passed to the initiator/acceptor. This > > OdbcLog will do true logging for all messages into the messages_log > > table. These messages are also persisted indefinitely. > > > > --oren > > > > > -------- Original Message -------- > > > Subject: [Quickfix-developers] Logging Incoming Messages in Database > > > ODBC > > > From: AS...@bo... > > > Date: Fri, February 19, 2010 5:17 am > > > To: qui...@li... > > > > > > > > > QuickFIX Documentation: > > http://www.quickfixengine.org/quickfix/doc/html/index.html > > > QuickFIX Support: http://www.quickfixengine.org/services.html > > > > > > > > > Hi, > > > > > > In our company we are using QuickFix Engine, and configure It to log > > > messages in database. > > > We use an ODBC connector , that connect to a Sql Serveur 2005 Database. > > > > > > The engine writes session data and outgoing messages in the database > > > "QuickFix" , table "messages" > > > but the Incomming messages are not logged in this table. > > > => How to do, to have also incomming messages ? > > > > > > - is this feature implemented or a configuration problem from our cfg > > file > > > ? > > > > > > thanks for your help. > > > > > > Alain SY > > > Bourse Direct > > > Service Informatique - Developpement > > > Tel : (00-33-0) 1-56-43-82-34 > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > > > Download Intel® Parallel Studio Eval > > > Try the new software tools for yourself. Speed compiling, find bugs > > > proactively, and fine-tune applications for parallel performance. > > > See why Intel Parallel Studio got high marks during beta. > > > http://p.sf.net/sfu/intel-sw-dev > > > _______________________________________________ > > > Quickfix-developers mailing list > > > Qui...@li... > > > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > > > > > > ------------------------------------------------------------------------------ > > > > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Quickfix-developers mailing list > > Qui...@li... > > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
