Forum

Please consider registering
guest

Members

Connect with:

Or log in with

Home

Forum

GlodaQuilla

GlodaQuilla shows "gloda id" in hexdecimal, but Gloda debuging shows messages.id column in decimal

Add Reply

Add Topic

Topic RSS

GlodaQuilla shows "gloda id" in hexdecimal, but Gloda debuging shows messages.id column in decimal

May 28, 2010
7:58 pm

WADA

Guest

Quote

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.

June 1, 2010
7:42 am

rkent

Admin

Forum Posts: 323

Member Since:
July 12, 2008

Offline

Quote

I've asked asuth and dascher their preferences for this in an email, as they were the ones who asked for these features.

June 1, 2010
1:47 pm

WADA

Guest

Quote

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 Wink