Oops, late catch of Monty-speak ;-). We're not working against ANSI 99 compliancy.....

parent fd5d367f
...@@ -3285,11 +3285,11 @@ for any usage. Even if we don't have the resources to do development ...@@ -3285,11 +3285,11 @@ for any usage. Even if we don't have the resources to do development
for every possible use, we are always willing to help and offer for every possible use, we are always willing to help and offer
suggestions to people that is trying to use MySQL in new territories. suggestions to people that is trying to use MySQL in new territories.
One of our main goals with the product is to continue to work against One of our main goals with the product is to continue to work towards
getting to be ANSI 99 compliant, but without sacrificing speed or ANSI 99 compliancy, but without sacrificing speed or reliability.
reliability. We are not afraid to add extensions to SQL or support for We are not afraid to add extensions to SQL or support for non-SQL
non-SQL features if this greatly increase the usability of MySQL for a features if this greatly increase the usability of MySQL for a big
big part of our users. (The new @code{HANDLER} interface in MySQL 4.0 part of our users. (The new @code{HANDLER} interface in MySQL 4.0
is an example of this strategy. @xref{HANDLER}.) is an example of this strategy. @xref{HANDLER}.)
We will continue to support transactional and not transactional We will continue to support transactional and not transactional
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment