[GH-ISSUE #183] Cannot write to previous row if constant_memory mode is enabled. #148

New issue

Closed

opened 2026-05-05 11:47:19 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 11:47:19 -06:00

Owner

Originally created by @igorko on GitHub (May 25, 2018).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/183

If constant_memory mode is enabled then writing to row e.g. 0 will produce empty cell, if there was already writing to row e.g. 1.

Originally created by @igorko on GitHub (May 25, 2018). Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/183 If constant_memory mode is enabled then writing to row e.g. 0 will produce empty cell, if there was already writing to row e.g. 1.

gitea-mirror closed this issue

2026-05-05 11:47:21 -06:00

gitea-mirror commented

2026-05-05 11:47:25 -06:00

Author

Owner

@jmcnamara commented on GitHub (May 25, 2018):

That is the documented behavior: http://libxlsxwriter.github.io/working_with_memory.html

The trade-off when using constant_memory mode is that data must be added sequentially in row order

@jmcnamara commented on GitHub (May 25, 2018): That is the documented behavior: http://libxlsxwriter.github.io/working_with_memory.html > The trade-off when using constant_memory mode is that data must be added sequentially in row order

gitea-mirror commented

2026-05-05 11:47:27 -06:00

Author

Owner

@igorko commented on GitHub (May 29, 2018):

Maybe it can be improved so flushing happens only after adding n-th row?

@igorko commented on GitHub (May 29, 2018): Maybe it can be improved so flushing happens only after adding n-th row?

gitea-mirror commented

2026-05-05 11:47:30 -06:00

Author

Owner

@jmcnamara commented on GitHub (May 29, 2018):

Maybe it can be improved so flushing happens only after adding n-th row?

That is something that could be handled in the end-user application with some simple buffering.

@jmcnamara commented on GitHub (May 29, 2018): > Maybe it can be improved so flushing happens only after adding n-th row? That is something that could be handled in the end-user application with some simple buffering.