ourdelta-developers team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxxxxx>]

Notes/ideas for 5.1 merge and future maintenance:

The innodb patches should be applied AFTER the innodb 1.0.1 plugin is
dropped in to storage/innobase

Perhaps it would make sense to carve up the patch, extract the parts that sit inside each engine.
This can help keep the innodb part sane on top of the plugin, as well as serve as an example for for instance adding PBXT support.
The infoschema support and rtlib mods to all the makefiles could also be separate I suppose.

Separating some of this before then trying partial merges could be a
good approach.


** Summary changed:

- Port userstatsV2 patch to 5.1, fix up reserved words
+ Port userstatsV2.1 patch to 5.1, fix up reserved words

** Description changed:

  Two small tasks, anybody can pick up:
  
  1) the userstatsv2 patch currently makes INDEX_STATISTICS etc reserved
- words in the parser. This is not necessary.
+ words in the parser. This is not necessary. [done - including other
+ cleanups - see comments below; patch version updated the V2.1]
  
- 2) Copy the patch to 5.1 and make sure it builds correctly. Probably
- best do to (1) first.
+ 2) Port the patch to 5.1 and make sure it builds correctly.

** Description changed:

  Two small tasks, anybody can pick up:
  
  1) the userstatsv2 patch currently makes INDEX_STATISTICS etc reserved
  words in the parser. This is not necessary. [done - including other
- cleanups - see comments below; patch version updated the V2.1]
+ cleanups - see comments below; patch version updated to V2.1]
  
  2) Port the patch to 5.1 and make sure it builds correctly.

-- 
Port userstatsV2.1 patch to 5.1, fix up reserved words
https://bugs.launchpad.net/bugs/284727
You received this bug notification because you are a member of OurDelta-
developers, which is the registrant for OurDelta.

Status in OurDelta - Builds for MySQL: In Progress
Status in OurDelta Series: trunk: In Progress

Bug description:
Two small tasks, anybody can pick up:

1) the userstatsv2 patch currently makes INDEX_STATISTICS etc reserved words in the parser. This is not necessary. [done - including other cleanups - see comments below; patch version updated to V2.1]

2) Port the patch to 5.1 and make sure it builds correctly.