Gregory Oschwald

If you want to verify a database, I would suggest using [mmdbverify](https://github.com/maxmind/mmdbverify). If you just want a basic sanity check and you have already checked the MD5 of the download,...

I am not sure if we will port mmdbverify to Java. We primarily use it internally and have not seen much customer interest in such a tool.

The writer and most readers only support a record size of 32 currently. This means the data section will be limited to 4 GB. Ideally, the writer would throw a...

Closing this as future development is focused on the [Go mmdbwriter module](https://github.com/maxmind/mmdbwriter).

Is it possible something is modifying the file after it opens, e.g., is the database being updated? Is the file on a network file system or something like that?

I am curious what your use case for the uint128 data type is. Currently, we don't actually use it and it hasn't received much thought. `big.Int` was chosen as that...

I believe these are all big endian architectures. Do you happen to know if it is failing on all big endian architectures that Debian supports?

One thing that I am confused by is 0.300003-1 seems to have built on most of these architectures but 0.300003-3 doesn't. Are you sure it isn't a packaging issue or...

Thanks for explaining that. It sounds like there might be a bug in the freeze/thaw code on big endian architectures.

We haven't had a chance to look at it too closely besides identifying it as likely an issue on big endian architectures. Unfortunately, we don't have easy access to big...