Before the addition of binary packaged assets into Go as a standard library feature, there were various tools to accomplish the same task. Some of them, such as https://github.com/GeertJohan/go.rice , could use an alternate embedding. Basically, instead of having the binary files packaged as Go code in the executable itself, they simply appended a .zip file to the binary, and accessed that directly.
Now, I am not suggesting that as a direct solution (though it may be, as Go does apparently support Zip64 which does away with the 4GB limit), but perhaps instead looking at how it does what it does, and adapting that to simply appending a sqlite or other single-file database format to the Go binary and using the same basic technique for accessing it. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/bf1b9b41-50b2-4221-8389-7d184e9bc8a5n%40googlegroups.com.
