--quote:
Hey J, Have you ever made a synth to dirt and dirt to synth SQL impression? I am not sure but I do not think you have a "synth only" surface in the new version do you? I only see D and T. Anyway, if you have written one I would love to do some datamining. D
--end quote--
First, natural dirt last start to synth surface today:
query start: 4/20/2010 8:08:05 PM query end: 4/20/2010 8:08:06 PM elapsed time: 1 seconds ` Data Window Settings: 999 Divisor Odds Cap: None ` SQL: SELECT * FROM STARTERHISTORY WHERE INSTR('KEE-TPX-APX-HOL-DMR-SAX-OSA-WOX-GGX-PID', TRACKLAST) = 0 AND INSTR('KEE-TPX-APX-HOL-DMR-SAX-OSA-WOX-GGX-PID', TRACK) > 0 AND INTSURFACE <= 3 AND SFSHIFT <= 3 ` ` Data Summary Win Place Show Mutuel Totals 746.80 757.00 867.10 Bet -1138.00 -1138.00 -1138.00 Gain -391.20 -381.00 -270.90 ` Wins 77 142 220 Plays 569 569 569 PCT .1353 .2496 .3866 ` ROI 0.6562 0.6652 0.7620 Avg Mut 9.70 5.33 3.94
Explanation:
WHERE INSTR('KEE-TPX-APX-HOL-DMR-SAX-OSA-WOX-GGX-PID', TRACKLAST) = 0
AND INTSURFACE <= 3
The above two lines create the constraint that the horse raced on a natural dirt surface last out.
Here, I'm using the INSTR command to compare a list of track codes (All of the track codes used are those with synth surfaces) to the track code value sitting in the TRACKLAST field of the starterhistory table. The = 0 condition means that no match was found... or put another way, values read from the table in the TRACKLAST field were something other than the list of track codes used: KEE-TPX-APX-HOL-DMR-SAX-OSA-WOX-GGX-PID.
That takes care of track codes. But we still have to deal with surface. Here I'm using the INTSURFACE field (always get your field names from the table schema) to ensure that races being evaluated weren't run on turf. The <= 3 value takes care of that.
The next two lines create the constraint that the horse is racing on a synth surface today:
AND INSTR('KEE-TPX-APX-HOL-DMR-SAX-OSA-WOX-GGX-PID', TRACK) > 0
AND SFSHIFT <= 3
Here again I'm using the INSTR command. But this time I'm using it to compare the track code list to the track field... which means I'm dealing with today's track.
The > 0 part means that a match was found... or that today's track code is in fact one of the track codes from the track code list.
Unfortunately, there is only room in the table for 255 fields. So I didn't have room to add an intsurfacelast field.
Not to worry though. We can still compare surface in last to surface today using Surface Shift... or the SFSHIFT field.
A peek at the Surface Shift values shown on the JCapper Supported Factors page shows that SFSHIFT <= 3 would get you any and all combinations of moves from one dirt course to another... synth included.
That gets you Natural Dirt to Synth.
-jp
.
~Edited by: jeff on: 4/21/2010 at: 2:05:36 AM~
|