Forum

GlodaQuilla shows gloda id in hexdecimal, but other tools such as Gloda debuging, SQLite Manager, sqlite3.exe shows message.id etc.  in decimal.

GlodaQuilla is better to show integer column in decimal instead of hexadecimal for ease of Gloda debugging.

Fllowing is comment from asuth in email.

It seems more likely that someone would be debugging usin
g SQLite poking (decimal) versus .msf hacking (hex). And once the msf's are replaced by SQLite, everybody gets to be decimal!

If "gloda id" comes from .msf instead of SQL access of SQLite3 table, I think current hexadecimal representaion is better than decimal for debugging. Understanding of "gloda id is shown in hexadecimal" by we Gloda Debbuging user is sufficient.

And, if it comes from .msf, I can expect "offset in offline-store" in addition to "on disk" will be implemented soon