Forum

 
Current User: Guest Login Register
Please consider registering


Register? | Lost Your Password?

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

Add a New Topic Reply to Post
UserPost

7:58 pm
May 28, 2010


WADA

Guest

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.

7:42 am
June 1, 2010


rkent

Admin

posts 140

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

1:47 pm
June 1, 2010


WADA

Guest

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

Reply to Post

Reply to Topic:
GlodaQuilla shows "gloda id" in hexdecimal, but Gloda debuging shows messages.id column in decimal

Guest Name (Required):

Guest Email (Required):

NOTE: New Posts are subject to administrator approval before being displayed

Smileys
Confused Cool Cry Embarassed Frown Kiss Laugh Smile Surprised Wink Yell
Post New Reply

Guest URL (required)

Math Required!
What is the sum of:
12 + 8