https://bugs.documentfoundation.org/show_bug.cgi?id=155384
--- Comment #12 from Pierre Fortin <[email protected]> --- (In reply to ady from comment #10) More specifically to your points... > While I can reproduce it when copying from the already-imported first column > (by selecting the first column _only_), it can be easily avoided when > initially importing the data (using either "Separated by" or "fixed width"), > precisely because there is more data on the right-side (duplicated in this > case). So... rather than fixing what I consider a rookie coding error, the user is expected to abandon work on a HUGE spreadsheet (often 14-15M rows) that takes 4 minutes just to load on a very capable CPU: Processors: 20 × 12th Gen Intel® Core™ i7-12700K (4@5GHz, [email protected], [email protected]) Memory: 125.5 GiB of RAM and 2TB + 4TB SSDs + 44TB on 6 platter drives in order to save a few milliseconds finding the max width of the incoming data? > OTOH, I think users shouldn't expect to look-up 7900 rows (or whatever) just > in order to find the data format before suggesting the columns' width. That > would probably be inefficient. Compared to 4 minutes to load a large file; that's not even noticeable. -- You are receiving this mail because: You are the assignee for the bug.
