Re: Storing a SHA1 checksum

2002-12-29 Thread Benjamin Pflugmann
On Sun 2002-12-29 at 05:28:57 -0500, [EMAIL PROTECTED] wrote: sql, table I'm storing a SHA1 checksum as varchar(20) binary in my application. After running a test, it seems MySQL will strip trailing spaces from a varchar column, even if it is binary! Yes, the BINARY keyword only

Re: Storing a SHA1 checksum

2002-12-29 Thread Stefan Hinz, iConnect \(Berlin\)
PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, December 29, 2002 12:34 PM Subject: Re: Storing a SHA1 checksum On Sun 2002-12-29 at 05:28:57 -0500, [EMAIL PROTECTED] wrote: sql, table I'm storing a SHA1 checksum as varchar(20) binary in my application. After running a test, it seems MySQL

RE: Storing a SHA1 checksum

2002-12-29 Thread Adolfo Bello
I would try storing the SHA1() result as a hexadecimal string. Adolfo -Original Message- From: Benjamin Pflugmann [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 29, 2002 7:35 AM To: Philip Mak Cc: [EMAIL PROTECTED] Subject: Re: Storing a SHA1 checksum On Sun 2002-12-29

Re: Storing a SHA1 checksum

2002-12-29 Thread Paul DuBois
At 5:28 -0500 12/29/02, Philip Mak wrote: sql, table I'm storing a SHA1 checksum as varchar(20) binary in my application. Other people have addressed other aspects of your message, but I'm curious why you're using a VARCHAR(20), when SHA1() returns a 40-byte string. After running a test, it

Re: Storing a SHA1 checksum

2002-12-29 Thread Philip Mak
On Sun, Dec 29, 2002 at 11:09:47PM -0600, Paul DuBois wrote: At 5:28 -0500 12/29/02, Philip Mak wrote: sql, table I'm storing a SHA1 checksum as varchar(20) binary in my application. Other people have addressed other aspects of your message, but I'm curious why you're using a VARCHAR(20),

Re: Storing a SHA1 checksum

2002-12-29 Thread Paul DuBois
At 0:14 -0500 12/30/02, Philip Mak wrote: On Sun, Dec 29, 2002 at 11:09:47PM -0600, Paul DuBois wrote: At 5:28 -0500 12/29/02, Philip Mak wrote: sql, table I'm storing a SHA1 checksum as varchar(20) binary in my application. Other people have addressed other aspects of your message, but