Bug in BLOB on 64bit AMD

Hello,

I've found a bug in mysql++, when a BLOB field is used which is not the 
only field returned from a query. This happens only when the query is
run on a 64bit machine (AMD64 in my case). To demonstrate, use the following 
table with the load_file and cgi_image examples:

CREATE TABLE fax ( id INTEGER AUTO_INCREMENT PRIMARY KEY,
                   fax BLOB );

execute load_file as usual.

Change cgi_image to return id and fax as a result of the select.

        query << "SELECT " << MY_KEY << "," << MY_FIELD << " FROM " << MY_TABLE
              << " WHERE " << MY_KEY << " = " << argv[1];
        ResUse res = query.use();
        Row row = res.fetch_row();
        long unsigned int *jj = res.fetch_lengths();
        cout << "Content-length: " << jj[1] << endl << endl;
        fwrite(row.raw_data(1), 1, jj[1], stdout);

jj[1] returns a proper length, but raw_data is not correct, and it looks
like a memory dump. I'm having difficulty debugging this, as I cannot
quite find where things go wrong.

Any ideas?

Grtz
Erwin

-- 
erwin@xxxxxxxxxxxxxx
  I pledge allegiance to the form of science fiction and fantasy and to
  the promise for which it stands: one world, polycultural, genetically
  engineered, with Internet access for all.    -- Tonio Roque

-- 
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:    
http://lists.mysql.com/plusplus?unsub=gcdmc-plusplus@xxxxxxxxxxx