Hi, As mentioned, I was already looking at byte arrays, therefore I was implying I was already using BINARY(16) for md5sum.
It now works and gives decent runtime performance, while saving more than 200MB on my 2GB+ H2 database. Thanks. Christian On Tue, Apr 24, 2012 at 8:19 AM, Thomas Mueller <[email protected]> wrote: > Hi, > > Yes, BINARY is the right data type for a hash / checksum. > > Regards, > Thomas > > > On Saturday, April 21, 2012, [email protected] wrote: >> >> On Fri, Apr 20, 2012 at 4:56 PM, Christian MICHON >> <[email protected]> wrote: >>> >>> Hi Steve, >>> >>> yes, after x millions of records, it would be nice to have the checksum >>> taking minimal space. >>> >> >> H2 has a BINARY SQL type mapped to byte[]. Most probably, you can't go >> lower than that >> >> -- >> Vasile Rotaru >> >> -- >> You received this message because you are subscribed to the Google Groups >> "H2 Database" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/h2-database?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
