|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | SQL UDM Quick Index File | |
| busseb 1/25/2011 11:13:04 PM | Can I make a Quick Index File for SQL like when I use the "Export/Quick Index File-Create New File" using Playlist Mode? ElPaso
| |
| jeff 1/26/2011 4:31:25 PM | Yes, but with limited functionality. Instructions: 1. Point the Data Window at your target folder. it doesn't matter whether the Data Window is in SQL mode or Playlist File mode. Just click the Folder Icon and double click a folder to set it as the current target folder. 2. Click MENU. Then select Exports, followed by either Quick Index File - Create New File or Quick Index File - Append (your choice.) 3. When the dialog box pops up, provide the name of the quick index file you want the data to be exported to and hit the Open button. 4. With the Data Window in SQL mode, hit the SQL button, provide a sql expression, and execute your query by hitting the Execute button. The Data Window will execute your query and write limited data for all of the starters returned by your query to the quick index file named in step #3 above. Why limited data? Which limited data? I programmed the SQL Mode Data Window to read and process data sitting in the starterhistory table as it exists in the starterhistory table. The objective when I did the programming for this was execution speed. The query in the above example is being executed with the Data Window in SQL mode - meaning that the Data Window is reading data returned by the query from the starterhistory table. Internally within the program, this is a completely different process from the routine that reads data from a pl_profile.txt file. When you use Data Window Exports to create a quick index file with the Data Window in sql mode, information about factors that are native to the starterhistory table will transfer over to the quick index file. Native factors include JPR, Alchemy, PRating, Cantrunxformattrib, etc. See the Table Schema for more detail. Factors that are not native to the table - meaning those added to your sql factor setup - the ones with slot numbers... F01, F02, F03, etc. will not transfer over and are not written to the quick index file in the above example. I could write a conversion routine to get those factors written to a quick index file -- but that would have the effect of slowing down the Sql Mode Data Window's query execution speed -- NOT something I am willing to do. If you want all of the factors found in a pl_profile.txt file to transfer over to a quick index file, there's only one way to accomplish that: Create a playlist file UDM that replicates your SQL UDM and run the replicated UDM through the Data Data Window with the Data Window in playlist file mode. One gotcha with that... Sql UDMs give you the ability to use OR conditionals. If the Sql UDM you want to replicate contains OR conditionals, then replication of your Sql UDM is going to take the form of creating multiple playlist file UDMs -- each designed in such a way that each replication UDM gets unique horses. Then, when you run the first one through the Data Window you will create a new quick index file -- and when you run subsequent UDMs through the Data Window you would append to the quick index file. Hope I explained that in a way that makes sense. -jp . ~Edited by: jeff on: 1/26/2011 at: 4:31:25 PM~
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |