|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | SQL Shipper | |
| GUGA 6/10/2010 8:40:40 PM | Is the "shipper" filter available in SQL? I haven't been able to locate it and just wanted to make sure I haven't overlooked it on the SQL Schema. Thanks, Scott and a sidenote ....could someone try using the trainer name MCCLELLAND PAUL G. in a SQL udm and let me know if the run routine picks out the "AND" in his name and places it as a new command line...or is it just a quirk on my machine LOL!! Scott ~Edited by: GUGA on: 6/10/2010 at: 8:40:40 PM~
| |
| Charlie James 6/10/2010 8:38:29 PM | No separate field for shipper. Instead use these two fields: track tracklast To make a sql udm flag shippers: AND INSTR(TRACK, TRACKLAST) = 0 AND STARTSLIFETIME > 0 In the above example startslifetime is needed to weed out FTS which have an empty value in the tracklast field. To make a sql udm avoid shippers: AND INSTR(TRACK, TRACKLAST) > 0 AND STARTSLIFETIME > 0 Btw, a year ago I was a sql illiterate. Amazing how you pick this stuff up just by working with it.
| |
| GUGA 6/10/2010 8:47:50 PM | Yeah I am quite illiterate so I am assuming that I would need to specify track last and track today as you have listed it. Mainly trying to model trainer moves and on a larger level I don't want to filter which track the horse is shipping from. How would I specify or model an individual trainer that ships today??
| |
| jeff 6/10/2010 9:22:52 PM | It's easy. Just add a trainer name match constraint to the existing shipper constraints. Suppose for the sake of argument you wanted to create a SQL UDM to identify Nick Zito's horses when he ships. Your expression might look something like this: INSTR(TRACK,TRACKLAST)=0 AND STARTSLIFETIME > 0 AND INSTR(TRAINER, 'ZITO NICHOLAS P') > 0 -jp .
| |
| GUGA 6/10/2010 9:24:53 PM | Thanks Jeff and Charlie!
| |
| jeff 6/11/2010 4:55:26 AM | --quote: and a sidenote ....could someone try using the trainer name MCCLELLAND PAUL G. in a SQL udm and let me know if the run routine picks out the "AND" in his name and places it as a new command line...or is it just a quirk on my machine LOL!! Scott --end quote-- Not a quirk on your machine. The interface is programmed to identify the word "AND" within the expression and move it to the next line. Had there been characters to the left of AND within the trainer name things would have been handled fine. My advice, if you want to use this trainer name in a UDM is to handle it as a special case. In the following example I've done that by using two separate INSTR commands. Note that each INSTR command evaluates a character string that is part of the full trainer name "MCCLELLAND PAUL G." Both character strings together make up the full trainer name. I've also strategically placed parenthesis characters (in red font) within the expression so that both INSTR commands must be greateer than zero (both character strings have to be part of the trainer name) before a name match is true. AND (INSTR(TRAINER, 'MCCLELLAN') > 0 OR INSTR(TRAINER,'PAUL G') > 0) EDIT: The expression can be simplified by removing the parenthesis characters and replacing OR with AND as follows: AND INSTR(TRAINER, 'MCCLELLAN') > 0 AND INSTR(TRAINER,'PAUL G') > 0 -jp . ~Edited by: jeff on: 6/11/2010 at: 4:55:26 AM~
| |
| NYMike 1/17/2025 5:13:33 PM | Is it possible to create a UDM in SQL that would identify a shipper that has run at today's track before, just not in the most recent race? Thanks, Mike
| |
| jeff 1/19/2025 10:58:46 PM | If you define "has run at the track before" to mean at today's track code: The answer is no. There really isn't. If you define "has run at the track before" to mean at today's track code and on today's course: The answer is a qualified Yes, but it depends on your SQL Factor Setup. If you have any of the "TDX" factors that contain "TRACK" as part of the factor name the answer is a qualified Yes. For example, suppose you have TDX_TRACK_CX10 assigned to slot #F35 in your SQL Factor Setup. If that's the case: Horses flagged by "AND VALF35 > 0" will have at least one past visible running line at today's Track Code on the same course (dirt, turf, tapeta, etc.) as today's race provided any surface changes have been processed. HOWEVER: 1. Only the 10 most recent running lines are visible in our files. (That was a decision I made in 2009 when I signed with HDW.) It's possible for horses to have raced at today's track code more than 10 starts ago. If a horse raced at today's track code on today's course in its 12th running line back: The horse isn't going to be flagged by "AND VALF35 > 0" 2. In JCapper, "TRACK" as part of the factor name means: at today's track code and on today's course. It's possible for horses to have raced at today's track code but on a different course than they are racing on in today's race. If that's the case, the horse isn't going to be flagged by "AND VALF35 > 0" What about non-sql identifiers? Same thing. If you look at the earnings or stat boxes in JCapper PPs you will see a line labeled as "Track." Same thing applies in the PPs as when "TRACK" as part of a TDX factor name. The numbers and best Fig displayed in the stat box are for the horse's past races at today's Track Code on the same course (dirt, turf, tapeta, etc.) as today's race. And even this needs to be qualified. If today's race was scheduled to be on the turf when HDW made the data file, and the race is later taken off the turf: The numbers in the stat boxes don't change. Fyi, I do not like that at all. And have trained myself to not look at that part of the stats boxes when races come off the turf. That's as accurate a description as I can give. -jp .
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |