On Fri, Jan 09, 2009 at 09:50:35AM +0000, Jan Rittinger wrote:

Update of /cvsroot/monetdb/pathfinder/compiler/Tests In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv17274/Tests

Modified Files: usage.stable.out usageH.stable.out Log Message: -- Adjust help messages to the new copyright information.

Just for info for you and for who ever will take care of updating the stable output accordingly in the Nov2008 release branch and then (not) propagating it to the development trunk (most probably Sjoerd or me ...):

The copyright information has obviously also been updated in the Nov2008 release branch, and the stable output for the respective tests should be updated there as well --- propagating these updates *might* then cause (probably easily resolvable) conflicts as the stable output in the development trunk has just experienced two changes: new copyright and new usage info.

Note, this is neither a critique nor a major problem, but just to share information that might help to reduce / prevent inconveniences, in particular with (semi-automa[tgn]ic) propagation of chnages from the latest release branch to the development trunk.

(For the future, the "ideal" procedure would (have) be(en) to first update the copyright info in the stable output of the release branch, then propagate these changes, and then update / extend the usage info in the development trunk and update the stable output there accordingly. ;-))

Stefan

-- Extend help message 'pf -H' to list all available optimization phases.

U usageH.stable.out Index: usageH.stable.out =================================================================== RCS file: /cvsroot/monetdb/pathfinder/compiler/Tests/usageH.stable.out,v retrieving revision 1.49 retrieving revision 1.50 diff -u -d -r1.49 -r1.50 --- usageH.stable.out 2 Dec 2008 17:30:41 -0000 1.49 +++ usageH.stable.out 9 Jan 2009 09:50:33 -0000 1.50 @@ -11,7 +11,7 @@ # 15:43:45 >

Pathfinder XQuery Compiler ($Revision$, $Date$) -(c) Database Group, Technische Universitaet Muenchen +(c) Database Systems Group, Eberhard Karls Universitaet Tuebingen

Usage: pf [OPTION] [FILE]

@@ -38,6 +38,9 @@ = -p, --physical-algebra-plan: enable generation of physical algebra plan = -f<format>, --format=<format>: enable generation of algebra properties + print all available properties (logical/physical algebra)

•     <optoptions> selectively choose optimization options that are based
  

•                  on a single property (e.g., 'O') to print the respective
  

•                  property
      c  print cost value (physical algebra)
      o  print orderings (physical algebra)
  
  

@@ -65,23 +68,30 @@ 21 after compiling the physical algebra into MIL code 22 after the MIL program has been serialized

-= -o<options>, --optimize-algebra=<options>: optimize algebra according to options: += -o<optoptions>, --optimize-algebra=<optoptions>: optimize algebra according to optimization options:

•     E  merge common subexpressions (CSE)
  

•     G  apply general optimization (without properties)
      O  apply optimization based on constant property
      I  apply optimization based on icols property
      K  apply optimization based on key property
  

•     C  apply optimization using multiple properties (complex)
  

•        (and icols based optimization will be applied afterwards)
  

•     G  apply general optimization (without properties)
  

•     N  apply optimization based on required node values property
      V  apply optimization based on required values property
  

•     [  map column names to unique column names
  

•     J  push down equi-joins (requires unique column names)
  

•     ]  map column names back (from unique names to original names)
  

•     M  apply optimization based on multi-value dependencies
      S  apply optimization based on set property
  

•     U  apply optimization based on XML Guide information
  

•        (only works for the SQL code generation)
  

•     C  apply optimization using multiple properties (complex)
  

•        (and icols based optimization will be applied afterwards)
  

•     J  push down equi-joins
  

•     M  push up cross products (based on multi-value dependencies
  

•     T  push up theta-joins (based on multi-value dependencies
  

•     R  push up rank operators
      }  introduce proxy operators that representoperator groups
      {  remove proxy operators
  

•     Q  apply optimizations tailored for the SQL code generation
  

•     [  assign a new set of unique column names
  

•     ]  assign bit-encoded column names (deprecated optimization option)
      P  infer all properties
  

•     _  does nothing (used for structuring the options)
  

•     _  does nothing (used for structuring the optimization options)
         (default for option -A is: '-o OIKCG_VG_JISI_GECSVR_OK_N}MT{JISI_GECSVR_}MT{JISI_OK_GECSVR_GP')
         (default for option -S is: '-o OIKCG_VG_JISI_GECSVR_OK_N}MT{JISI_GECSVR_Q_}MT{JISI_OK_GECSVR_QGP')
  
  
  

U usage.stable.out Index: usage.stable.out =================================================================== RCS file: /cvsroot/monetdb/pathfinder/compiler/Tests/usage.stable.out,v retrieving revision 1.19 retrieving revision 1.20 diff -u -d -r1.19 -r1.20 --- usage.stable.out 19 Jun 2008 14:13:10 -0000 1.19 +++ usage.stable.out 9 Jan 2009 09:50:33 -0000 1.20 @@ -11,7 +11,7 @@ # 13:16:47 >

Pathfinder XQuery Compiler ($Revision$, $Date$) -(c) Database Group, Technische Universitaet Muenchen +(c) Database Systems Group, Eberhard Karls Universitaet Tuebingen

Usage: pf [OPTION] [FILE]

---

Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Monetdb-pf-checkins mailing list Monetdb-pf-checkins@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins