<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi.<br><br>You may add: <br>transaction-isolation = SERIALIZABLE<br>in your MySQL configuration file, my.cnf, in the [mysqld] section.<br><br>But, if you can't use a 2007 testing database with 2008/2009 shim code. The database structure has changed...<br><br>Sam.<br><br><br>--- En date de : <b>Lun 12.1.09, Justin <i><justins@ftml.net></i></b> a écrit :<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">De: Justin <justins@ftml.net><br>Objet: Re: [ts-gen] setting up mysql and editing data.c and once.c in shim/src directory<br>À: "trading-shim general mailing list" <ts-general@trading-shim.org>, "trading-shim general mailing list" <ts-general@trading-shim.org><br>Date: Lundi 12 Janvier 2009, 5h52<br><br><pre>Thank you Russ<br><br>I completely skipped the paragraph at the top
explaining the use of the<br>info <br>pre 2007 and post 2007. I've kept the database the same for now. Logged<br>into my <br>mysql as root, changed to the "mysql" database, created the user shim<br>with no <br>password, granted all privileges on testing and gave shim@localhost<br>super and <br>create temporary tables. <br><br>mysql> SHOW GRANTS FOR 'shim'@'localhost';<br>+---------------------------------------------------------------------------------------------------------------------+<br>| Grants for shim@localhost <br> |<br>+---------------------------------------------------------------------------------------------------------------------+<br>| GRANT SUPER, CREATE TEMPORARY TABLES ON *.* TO<br>'shim'@'localhost' WITH<br>GRANT OPTION | <br>| GRANT ALL PRIVILEGES ON `testing`.* TO 'shim'@'localhost' <br> <br>
| <br>+---------------------------------------------------------------------------------------------------------------------+<br>2 rows in set (0.00 sec)<br><br>I haven't changed a thing in .shimrc<br><br>DbmsName mysql<br>DbmsHost localhost<br>TableSet testing<br>UserName shim<br>Password 0<br>FeedName tws<br>FeedHost localhost<br>FeedPort 7496<br>HqPeriod 11<br>ClientId 8 <br>Upstream paper <br>LogFiles log<br>PollTime 2<br><br>I started my demo TWS "Enabled ActiveX and Socket Clients" and added<br>the<br>localhost<br>ip 127.0.0.1 to the trusted IP addresses. <br><br>When I try and test shim with "shim --data" I get:<br><br>Problem: 512 mySQL isolation level must be serial<br>Exiting<br><br>I thought I had all the pieces of the puzzle in place, I must have<br>missed something <br>along the way. Of the top of my head,
quick question for you, once this<br>program works<br>smoothly could it access a stripped down version of the TWS, one that<br>would run as a<br>demon in the background, removing the GUI altogether?<br><br>Justin <br><br><br><br>On Sun, 11 Jan 2009 17:16:27 -0500 (EST), "R P Herrold"<br><herrold@owlriver.com> said:<br>> On Sat, 10 Jan 2009, Justin wrote:<br>> <br>> ><br>> > I've run into a bit of a problem with understanding how I'm<br>to add the<br>> > lines below in<br>> > the two files mentions.<br>> <br>> <br>> The example cited was related to doing edits to set up <br>> userid's and such for using the database, with other than <br>> 'stock' values, and written using a February 2007 version of <br>> the sources as an example. In the last two years, we have <br>> come VERY FAR past that need, and I need to revisit that pate; <br>> I'll take a look when in the office Monday.<br>>
<br>> > I did some looking around at some examples of code from C++ <br>> > and Ruby and it seems to me to be C++ code. What I need to <br>> > know is how to properly introduce the lines below,<br>> <br>> The good news is that you no longer need to do those source <br>> code edits, and can simply drop the variable / value pair into <br>> the .shimrc There is a sample in any recent tarball; the <br>> release from Friday looks like this:<br>> <br>> <br>> [herrold@centos-5 shim-090109]$ cat .shimrc<br>> DbmsName mysql<br>> DbmsHost localhost<br>> TableSet testing<br>> UserName shim<br>> Password 0<br>> FeedName tws<br>> FeedHost localhost<br>> FeedPort 7496<br>> HqPeriod 11<br>> ClientId 8<br>> Upstream paper<br>> LogFiles log<br>> PollTime 2<br>> [herrold@centos-5
shim-090109]$<br>> <br>> The first four entries are simple to edit. My working copy <br>> (which connects on host: xeon.first.lan to a database: <br>> rph_testing under userid: rph_shim with NO password), looks <br>> like this:<br>> <br>> <br>> [herrold@centos-5 ~]$ cat .shimrc<br>> DbmsHost xeon.first.lan<br>> UserName rph_shim<br>> TableSet rph_testing<br>> ...<br>> <br>> Note that these are not order sensitive.<br>> <br>> <br>> The .shimrc file was added, after Bill and I discovered that I <br>> was 'stepping on' his working dataset, with a failed source <br>> code patch for like the third time. (additionally I moved my <br>> MySQL server and dataset to another computer -- it can be <br>> really difficult to debug a side effect which neither person <br>> is looking for)<br>> <br>> > but honestly I don't see how to do this without spending <br>>
> hours maybe days learning basic C++ code, that is to say if <br>> > I'm right about it being C++ code.<br>> <br>> outlined above, and no source edits needed.<br>> <br>> Part of the benefit of coming to the project now is that we <br>> are three years in, and so as others had to do this, we <br>> responded to their confusion with the .shimrc file mechanism. <br>> We have one fairly minor set of additions to that file, and to <br>> the initiialization process left on our roadmap before we will <br>> move the project from a 'beta' to a 'production stable'<br>status <br>> [there are some other milestones in the code as well, which we <br>> need as well]. The changes will be largely invisible to an <br>> external user, and any recent writeup of the .shimrc in teh <br>> mailing list archive will be substantailly complete.<br>> <br>> Welcome, by the way.<br>> <br>> For the wider audience, we are
largely complete with the <br>> development cutover to the Debian 'lenny' (and once security <br>> updates are underway well in 'testing', back to<br>'testing'). <br>> A final member computer to run Debian 'lenny' in the distcc <br>> buildfarm which Bill uses to speed incremental testing and <br>> development arrived yesterday, and I will slot it in Monday.<br>> <br>> Additionally Friday's release builds and runs cleanly on the <br>> following platforms in production:<br>> <br>> Debian 'testing' 32 bit (i386)<br>> Debian 'lenny' 64 bit (amd64)<br>> OS/X 10.4 PPC (32 bit)<br>> CentOS 5 32 bit (i686)<br>> CentOS 5 64 bit (x86_64 multilib)<br>> RHEL 4 64 bit (s390 multilib)<br>> <br>> I will speak with the IBM 'chiphopper' team, to get access to <br>> Power 5 (64 bit) RHEL turned on for verification of function; <br>> I anticipate no surprises or problems there
at all.<br>> <br>> The remaining possible platform (Windows 2000 and later with <br>> Cygwin 1.7) has a build problem with the MySQL libraries at <br>> the moment, and so we do not have function there at the <br>> moment.<br>> <br>> -- Russ herrold<br>> _______________________________________________<br>> ts-general mailing list<br>> ts-general@trading-shim.org<br>> http://www.trading-shim.org/mailman/listinfo/ts-general<br>-- <br> Justin<br> justins@ftml.net<br><br>-- <br>http://www.fastmail.fm - Or how I learned to stop worrying and<br> love email again<br><br>_______________________________________________<br>ts-general mailing list<br>ts-general@trading-shim.org<br>http://www.trading-shim.org/mailman/listinfo/ts-general<br></pre></blockquote></td></tr></table><br>