Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.8.6

Request #14985 Problems with atomic index updates
Submitted: 2008-11-10 15:26 UTC
From: yunosh Assigned:
Status: Open Package: MDB2_Schema (version 0.8.2)
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 28 - 17 = ?

 
 [2008-11-10 15:26 UTC] yunosh (Jan Schneider)
Description: ------------ Indexes are updated in one step when updating database schemas. This leads to problems because both, changing column definitions before, or after the indexes might not work. One example: updating column widths might exceed the maximum index length of 1000 in MySQL, even though an index update would eliminate that index at a later step. Thus, index updates should be split up, all changed/deleted indexes should be removed first, then the columns should be updated, then changed/added indexes should be added.

Comments

 [2008-11-15 18:52 UTC] ifeghali (Igor Feghali)
Hello Jan, If i understand correctly this is related to Bug #12154. We have to wait a fix there first. Regards, Igor.