Ignore:
Timestamp:
Nov 6, 2007, 9:42:09 AM (14 years ago)
Author:
Nicklas Nordborg
Message:

Fixes #811: Wildcard or regular expressions in raw data column mappings

To be consistent with exact name matching the first column found is always returned

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/src/docbook/admindoc/plugin_installation.xml

    r3871 r3911  
    13721372              mapping has better performance and we recommend that you use
    13731373              it unless you have to recalculate any of the numerical values.
     1374              In both cases, if no column matching the placeholder exactly is found
     1375              the placeholder is interpreted as a regular expression that
     1376              is matched against each column. The first one found is used.
    13741377              Here are a few mapping examples:
    13751378            </para>
    13761379           
    13771380<informalexample>
    1378 <literallayout>\Name\
    1379 \1\
    1380 [\row\, \column\]
    1381 =2 * col('radius')
     1381<literallayout>\Name\ --&gt; exact match is required
     1382\1\ --&gt; column with index 1 (the second column)
     1383[\row\, \column\] --&gt; combining row and column to a single coordinate
     1384=2 * col('radius') --&gt; calculate the diameter dynamically
     1385\F63(3|5) Median\ --&gt; use regular expression to match either F633 or F635
    13821386</literallayout>
    13831387</informalexample>
Note: See TracChangeset for help on using the changeset viewer.