This can be fixed with this patch, please try it; however I wonder what's the best thing to do, as the rest of the Designer code does not support creating a relation with such a compounded key. Tell me your opinion.
About your question, I'm not the best guy to answer because I'm not a PMA developer. But, my intention in resolve this bug was only cosmetic. The designer visual it's better now and if I need print my database design, I'll understand better what I did. Finally, I think that this fix should go to release.
Thank you a lot more a time and sorry by my horrible english.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the feedback. I'll commit the fix later today. Please do not close this tracker entry, we close it only when the corresponding release is published.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Appointments
This can be fixed with this patch, please try it; however I wonder what's the best thing to do, as the rest of the Designer code does not support creating a relation with such a compounded key. Tell me your opinion.
Index: pmd_common.php
--- pmd_common.php (revision 12226)
+++ pmd_common.php (copie de travail)
@@ -218,8 +218,10 @@
if ($unique_only && ! $index->isUnique()) {
continue;
}
- $column = key($index->getColumns());
- $keys[$schema . '.' .$table . '.' . $column] = 1;
+ $columns = $index->getColumns();
+ foreach ($columns as $column_name => $dummy) {
+ $keys[$schema . '.' .$table . '.' . $column_name] = 1;
+ }
}
}
Thanks, now it's fixed.
About your question, I'm not the best guy to answer because I'm not a PMA developer. But, my intention in resolve this bug was only cosmetic. The designer visual it's better now and if I need print my database design, I'll understand better what I did. Finally, I think that this fix should go to release.
Thank you a lot more a time and sorry by my horrible english.
Thanks for the feedback. I'll commit the fix later today. Please do not close this tracker entry, we close it only when the corresponding release is published.
Ok, sorry. It was my first bug report, I didn't know. :)
Fixed in subversion, thanks for reporting.