Comments for New Features In MySQL 6.x http://blogs.mysql.com/peterg By MySQL development-department workers Sat, 07 Nov 2009 20:47:17 +0000 http://wordpress.org/?v=2.6.1 Comment on MySQL 5.4 by peterg http://blogs.mysql.com/peterg/2009/05/20/mysql-54/#comment-4703 peterg Mon, 02 Nov 2009 18:30:09 +0000 http://blogs.mysql.com/peterg/?p=89#comment-4703 > Do you know if WL#1326 will make it into 5.4? No. > Do you know if WL#1326 will make it into 5.4?
No.

]]> Comment on MySQL 5.4 by Jon http://blogs.mysql.com/peterg/2009/05/20/mysql-54/#comment-4671 Jon Sat, 31 Oct 2009 19:47:00 +0000 http://blogs.mysql.com/peterg/?p=89#comment-4671 Do you know if WL#1326 will make it into 5.4? Do you know if WL#1326 will make it into 5.4?

]]> Comment on Fractional seconds precision in MySQL datetime data types by Darren Cassar http://blogs.mysql.com/peterg/2009/08/07/fractional-seconds-precision-in-mysql-datetime-data-types/#comment-3870 Darren Cassar Fri, 07 Aug 2009 18:49:03 +0000 http://blogs.mysql.com/peterg/?p=114#comment-3870 Two Words Peter :) .... THANK YOU I'm glad this has been in your roadmap all along, and I'm sure many others appreciate the effort in implementing this feature as much as I do. Cheers, Darren Two Words Peter :) …. THANK YOU
I’m glad this has been in your roadmap all along, and I’m sure many others appreciate the effort in implementing this feature as much as I do.

Cheers,
Darren

]]> Comment on The Roadmap by MySQL :: New Features In MySQL 6.x http://blogs.mysql.com/peterg/2008/05/04/the-roadmap/#comment-3869 MySQL :: New Features In MySQL 6.x Fri, 07 Aug 2009 16:48:52 +0000 http://blogs.mysql.com/peterg/2008/05/04/the-roadmap/#comment-3869 [...] my 2008-05-04 blog posting about the roadmap, I included WL#946 in a list with the heading “Let’s not forget that these will fit in [...] [...] my 2008-05-04 blog posting about the roadmap, I included WL#946 in a list with the heading “Let’s not forget that these will fit in [...]

]]> Comment on WL#411 actually is about generated non-always-virtual columns by peterg http://blogs.mysql.com/peterg/2009/08/01/wl411-actually-is-about-generated-non-always-virtual-columns/#comment-3836 peterg Tue, 04 Aug 2009 16:17:36 +0000 http://blogs.mysql.com/peterg/?p=112#comment-3836 WL#411 says that OLD/NEW values won't work. And it says BEFORE triggers happen before generation, so they couldn't "override". And maybe non-deterministic generation should be illegal, but we have a hard time catching them. WL#411 says that OLD/NEW values won’t work.
And it says BEFORE triggers happen before generation, so they couldn’t “override”.
And maybe non-deterministic generation should be illegal, but we have a hard time catching them.

]]> Comment on WL#411 actually is about generated non-always-virtual columns by Justin Swanhart http://blogs.mysql.com/peterg/2009/08/01/wl411-actually-is-about-generated-non-always-virtual-columns/#comment-3828 Justin Swanhart Tue, 04 Aug 2009 04:08:13 +0000 http://blogs.mysql.com/peterg/?p=112#comment-3828 How will OLD/NEW values for these virtual columns work? Will a trigger be able to override a value generated at storage time for persistent values? Should non-deterministic generation clauses even be allowed? How will OLD/NEW values for these virtual columns work? Will a trigger be able to override a value generated at storage time for persistent values?

Should non-deterministic generation clauses even be allowed?

]]> Comment on Explain statements that aren’t SELECTs by Mark Callaghan http://blogs.mysql.com/peterg/2009/07/30/explain-statements-that-arent-selects/#comment-3783 Mark Callaghan Fri, 31 Jul 2009 15:13:54 +0000 http://blogs.mysql.com/peterg/?p=110#comment-3783 Production servers that I support have been hurt when someone used EXPLAIN of a select statement to understand the plan for a delete statement. The query used an index and the delete statement used a full table scan, thus locking all rows on a busy table. Insert/update/delete use different code in the optimizer. We need a real solution. Production servers that I support have been hurt when someone used EXPLAIN of a select statement to understand the plan for a delete statement. The query used an index and the delete statement used a full table scan, thus locking all rows on a busy table. Insert/update/delete use different code in the optimizer. We need a real solution.

]]> Comment on Explain statements that aren’t SELECTs by Roland Bouman http://blogs.mysql.com/peterg/2009/07/30/explain-statements-that-arent-selects/#comment-3781 Roland Bouman Fri, 31 Jul 2009 10:02:50 +0000 http://blogs.mysql.com/peterg/?p=110#comment-3781 Hi! I agree with Arjen on this one. If you transform the original EXPLAIN statement to a EXPLAIN SELECT statement, and you can't guarantee that the plan will be the same, then please don't. It does more harm than good, leaving the users chasing red herrings. Hi!

I agree with Arjen on this one.

If you transform the original EXPLAIN statement to a EXPLAIN SELECT statement, and you can’t guarantee that the plan will be the same, then please don’t. It does more harm than good, leaving the users chasing red herrings.

]]> Comment on Explain statements that aren’t SELECTs by Arjen Lentz http://blogs.mysql.com/peterg/2009/07/30/explain-statements-that-arent-selects/#comment-3779 Arjen Lentz Thu, 30 Jul 2009 23:04:22 +0000 http://blogs.mysql.com/peterg/?p=110#comment-3779 The current implementation of EXPLAIN (SELECT) is not suitable for anything else. Transforming other queries into SELECTs does not necessarily result in the same execution plan, and is therefore useless. The current implementation of EXPLAIN (SELECT) is not suitable for anything else. Transforming other queries into SELECTs does not necessarily result in the same execution plan, and is therefore useless.

]]> Comment on Azalea buds by Roland Bouman http://blogs.mysql.com/peterg/2009/07/13/azalea-buds/#comment-3557 Roland Bouman Mon, 13 Jul 2009 22:04:36 +0000 http://blogs.mysql.com/peterg/?p=106#comment-3557 Hi Peter! I'm very happy with these new features! Thanks for the information, this was really helpful. kind regards, Roland Hi Peter!

I’m very happy with these new features! Thanks for the information, this was really helpful.

kind regards,

Roland

]]>