OK for now, but for how long? I still think that 140 is going to come back and bite you in the rear end sometime when you're not expecting it. As I understand it, you have a short collection of bytes that is the result of encrypting a short string. You have much less than 140 bytes of data to store. You are storing four bytes (or whatever) of encrypted data, followed by 136 bytes of random crud. When it finally comes time to extract the encrypted data from the database and unencrypt it, your unencryption algorithm isn't going to know what to with those extra 136 bytes, and you'll get junk.
And as I said in my last message, NULL is not a valid choice for the fifth argument. The fact that it works does not change the fact that it is not valid. Please choose an appropriate value as listed in the documentation for that parameter. Always write code as though the next person to look at it just graduated from college and never wrote a line of professional code in his life. For one thing, you may come back to it in two years and ask yourself, "Why the heck did I do THAT?" RobR -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of YAN HONG YE Sent: Thursday, August 02, 2012 3:20 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] sqlite3_stat problem (YAN HONG YE) sqlite3_bind_text(stat,1,uu2,140,NULL); change to sqlite3_bind_blob(stat,1,uu2,140,NULL); it's ok! thank you! _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
