https://issues.apache.org/ooo/show_bug.cgi?id=124109
--- Comment #12 from Sam Jennings <[email protected]> --- I believe we should wait on that. There -is- a crash/data loss bug under the surface somewhere, and I think it would be hasty to sweep it from the records. Granted, the file I submitted was made from scratch, and it only demonstrates the column deletion bug, but no associated crash. Clearly something is lacking in the file which was present in the original. I *made* that file to replicate the circumstances of the original crash, but it was not the original crash file, and as it turns out, that file only caused the column deletion bug. However, I might still be able to get that crash to happen using a descendant of the original file, which still has a descendant of the table that used to cause the crash, before I modified it (from a user perspective, trying to work around the crash) and then unthinkingly saved it over its predecessor. If this bug report were to be closed and merged, or refiled, it should carry all elements of description of the column deletion bug, which is definitely not the desired behavior -- multi column tables are deleted on single column deletion, and in other cases multi column tables get badly mangled... this is NOT desired behavior, and it is an open bug...expected as known, perhaps, but definitely not good behavior. It should also carry mention of the crash (there has been at least one report, etc). I will get working on trying to modify the descendent file to see if I can get it to crash again. Meanwhile, can you share the bug report number for the other bug ...you say it's the same bug. I'd like to see it and read it. Thanks! -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
