Streaming API about xlsx HOT 3 CLOSED

You can use doc.Save to write content as a stream. Here's an example in Go:

package main

import (
    "io"
    "os"

    "github.com/gofika/xlsx"
)

func main() {
    // open file to write
    f, err := os.OpenFile("output.xlsx", os.O_CREATE|os.O_WRONLY, 0644)
    if err != nil {
        panic(err)
    }
    defer f.Close()

    doc := xlsx.NewFile()

    // do something with doc
    // ...

    // write to file or any io.Writer as stream
    doc.Save(f)
}

The core goal of my library is to use memory as much as possible to store file data in order to achieve the highest performance.

xlsx.File does not have a Close function because all modifications to the data are done in memory starting from xlsx.NewFile or xlsx.OpenFile. The document data in memory is written out only when SaveFile or Write is called.

from xlsx.

So you're saying, using doc.Save will flush the current data out of memory to the file so I can safely call it multiple times? And what happens to the previously constructed rows? I can save to the file every X amount of rows but I'm not sure if the memory will keep growing

from xlsx.

doc.Save writes out the document data in memory, but it does not clear the current memory information. It is safe to call doc.Save multiple times. All building actions are done in memory. Even if you save the file every X lines, the memory will still increase as the document data increases.

The purpose of this library's design is to operate xlsx files with the highest performance, and it is not specifically optimized for small devices such as embedded systems. If you are working with an xlsx document larger than 1GB, it is recommended that your hardware memory be larger than 1GB.

from xlsx.