Hi, Yes I would like contribute with documentation, not only with doc, but with > patchs too >
OK good to know! > Just for confirmation, and still on the join selectivity, is there any > treatment in this on code? > I think this is a important information for the join ordering problem.Derby talks about this > here<http://db.apache.org/derby/docs/10.8/tuning/tuning-single.html#ctunstats849251>, > and Postgres > here<http://www.postgresql.org/docs/9.0/static/row-estimation-examples.html> > . > H2 calculates the selectivity of each column. It also knows the number of rows per table. From this information, it calculates the estimated cost to use an index. See also: http://h2database.com/html/performance.html#explain_plan http://h2database.com/html/grammar.html#analyze > About the planner, what are your priorities, to I can contribute to > project? > The priorities are listed in the roadmap. The higher an item in the road map, the higher the priority. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
