This is a Safe Harbor Front slide, one of two Safe Harbor Statement slides included in this template.
One of the Safe Harbor slides must be used if your presentation covers material affected by Oracle’s Revenue Recognition Policy
To learn more about this policy, e-mail: Revrec-americasiebc_us@oracle.com
For internal communication, Safe Harbor Statements are not required. However, there is an applicable disclaimer (Exhibit E) that should be used, found in the Oracle Revenue Recognition Policy for Future Product Communications. Copy and paste this link into a web browser, to find out more information.
http://my.oracle.com/site/fin/gfo/GlobalProcesses/cnt452504.pdf
For all external communications such as press release, roadmaps, PowerPoint presentations, Safe Harbor Statements are required. You can refer to the link mentioned above to find out additional information/disclaimers required depending on your audience.
Very good example: MySQL 5.7 GA!
Go through at high level, Tomas will dive into the details.
Huge performance gains
Huge performance gains
Huge performance gains
Huge performance gains
9
10
As you may know, MySQL supports a plugin API that enables creation of server components. Plugins can be loaded at server startup, or loaded and unloaded at runtime without restarting the server.
In 5.7, we provide you two rewrite APIs so that you can write your own plugin.
Pre parse API: interface is query text, you rewrite queries by replacing text with other text
Post parse API: you have to modify the parse tree. May not be as difficult as it sounds. We offer a parser service through the plugin API. It contains methods to invoke parsing, get a normalized query text from parser tree, walk the parse tree.
In addition to providing interfaces for writing your own plugin, we also provide a production quality query rewrite plugin which rewrites queries without the need to make application changes. You can use this plugin to add hints, mofify join order and more.
Our query rewrite plugin uses the post parse plug-in interface, because it gives next to zero performanc overhead. I will explain how this works.
The main point of choosing post parsing is that digest is computed during parsing, and we use the digest to match incoming query with rules.
Still has to examine full index, but now it is just an index of the values all extracted. It is much smaller.
Started out as the Generic Geometry Library by OSGeo. Now it’s of course part of Boost.