Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Depending on the kind of query component you're using, I would imagine you could do this using a command-line grep (or any other text-searching tool) on your project folders. In the DFM, for normal TQuery-alike components, you're going to have something along the lines of </p> <pre> SQL.Strings=( 'select * from mytable' ) </pre> <p>or possibly (I've no Delphi to hand to check, the joys of being at home!)</p> <pre> SQL.Text=( 'select * from mytable' ) </pre> <p>Given how these strings can spread over several 'lines' inside the DFM, and given how there might be several variations you'd need to check for, personally I'd write a small piece of Delphi to do this.</p> <p>The basic idea would be; iterate through all the files/subfolders in a given directory, looking for all the DFM files, and for each one, read it into a TStringList, check for any of the TQuery (etc) SQL properties you're interested in, and write the results (component name, filename, actual SQL string) out to a results file. Really shouldn't be more than an hour or two's work at the most.</p> <p>If you have stored procs, that you call using something other than a TQuery-type component, you'll have to have a peek inside a DFM first and see how the SQL appears; it will probably be along the lines of</p> <pre> CommandText=( 'exec mysproc :id, :value' ) </pre> <p>etc.</p> <p>edit: Following the discussion in the comments, here's a sample from one of my DFMs;</p> <pre> (other properties) SQL.Strings = ( 'SELECT D.*, ' 'C.DESCRIPTION AS CLASS_DESCRIPTION, ' 'C.CHQ_NUM_THRESHOLD AS CLASS_CHQ_NUM_THRESHOLD,' 'C.CREDIT_LIMIT AS CLASS_CREDIT_LIMIT,' 'A.REF AS ACCOUNT_REF,' 'A.SORT_CODE AS ACCOUNT_SORT_CODE,' 'A.ACCOUNT_NUMBER AS ACCOUNT_ACCOUNT_NUMBER,' 'A.PREFERRED_ACCOUNT AS ACCOUNT_PREFERRED_ACCOUNT' 'FROM ' 'DRAWER_ACCOUNTS A LEFT JOIN DRAWERS D ' 'ON D.REF=A.DRAWER_REF' 'LEFT JOIN REF_DRAWER_CLASSES C' 'ON D.DRAWER_CLASS = C.CLASS_ID' 'WHERE A.SORT_CODE=:PSORT AND A.ACCOUNT_NUMBER=:PACC') (other properties) </pre> <p>So all I really need to do is to spot the <code>SQL.Strings = (</code> bit, then read the rest of the line and all subsequent lines, removing the leading and trailing <code>'</code>, until I get to a line that ends in <code>')'</code> - at which point I'm done. Whatever interesting SQL (and comments) might have been contained within the quotes on each line is irrelevant, really. You want to read each line that you're interested in and cut out the text between the first and last quote on each line. This must work because I can't see how Delphi would stream this any other way itself, it can't possibly 'read' the string contents - it's just working on the basis that the stringlist is (possibly) broken into lines and each line is delimited in the DFM with an opening and closing <code>'</code>, and the whole stringlist contents themselves are contained within a pair of brackets.</p> <p>Does that make sense, or am I still missing something? :-)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COSQL commands can include ( and ) (and comments (including ( and ))) so parsing will be a little difficult, because ) also terminates the SQL String... And how about Unicode, if the SQL Text contains special characters in comments or field values. But I guess that will be the fun and easy part :P
      singulars
    2. COVery true... but if you start parsing at the first ' and keep a count of how many levels of quote you're "in" as you go, you ought to be fine. At the end of the day, the Delphi DFM parser must be able to make sense of the string such that it does start and end with a quote. The SQL Text can't contain unicode unless the DFM file is unicode itself (unless I'm missing something about strings in DFMs!) so you could test for a unicode file first - I have some code here in SO somewhere that checks a file to see if it's unicode. Like you say, it's all part of the fun! :-)
      singulars
    3. CODelphi's not ideal for this unless you use the RegExp library. I would recommend writing a PERL script to parse the DFM and extract the SQL. I did something similar to convert TTable/TQuery components to the DOA "equivalents" and that involved keeping the pas & dfm in synch as you were modifying the files. Use the right tool for the job. In this case a scripting language with a good implementation of regular expressions. PERL might not be your cup of tea but you should be able to find something you like Python, Ruby?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload