Making sense of database byte code

Question

Hello,
I am having a lot of trouble with secondary indexes. I am getting garble when trying to read the key from the secondary index, and I cannot tell if this is from when I set the key or when I read the key. So I am trying to read my database dump to see if it was input correctly.
Here is my primary database. The first row is the key.
$ cat r1.csv
1 1 1 1.3 1.2
2 2 2 0.9 0.6
3 3 3 0.2 0.7
4 4 4 0.4 2.1
5 5 5 0.1 1.3
I just want to be able to read the contents. I am using C++ and these numbers are all stored as doubles (8 bytes). I am lining them up together with a char* to set the data of each Dbt. This file is working because I get the same values back out that I put in.
Here is a dump of the file once created. (Note: The order of the rows are probably different then from the CSV).
$ db_dump r1_un.db
VERSION=3
format=bytevalue
type=btree
db_pagesize=16384
HEADER=END
000000000000f03f
000000000000f03f000000000000f03f000000000000f03fcdccccccccccf43f333333333333f33f
0000000000000040
000000000000004000000000000000400000000000000040cdccccccccccec3f333333333333e33f
0000000000000840
0000000000000840000000000000084000000000000008409a9999999999c93f666666666666e63f
0000000000001040
0000000000001040000000000000104000000000000010409a9999999999d93fcdcccccccccc0040
0000000000001440
0000000000001440000000000000144000000000000014409a9999999999b93fcdccccccccccf43f
DATA=END
My question is how do I understand this?
"000000000000f03f" should be HEX for some single digit number. But using a 64bit IEEE floating point calculator says this means: 3.0386500000000000e-319
Am I reading this incorrectly? I tried reversing the bits, subtracting values and using "db_dump -p".

Answer 1

Hi,
You may try using "db_dump -p -d a ..." to get a better output, that may be easier to interpret.
You may also post here some relevant snippets from your code, such as the part where you're writing data into the primary database, the part where you read the data using the secondary index, the code for the secondary key callback function, and the exact structure and size of the key/data pairs.
Regards,
Andrei