> Something I forgot to mention earlier: If the files are not too big, > consider generating the SHA-512 on the fly instead of storing it. > Space-wise, it is the best possible optimization, obviously. And it > frees you from having to ensure consistency between the file and the hash. >
We're using MS SQL server... But we're using the SHA-512 to validate file integrity through a multistage process. So, we need to have the SHA for certain steps of the process. (eg. Ingress, Conversion, Output) so that we can validate it's the same file we received, etc. The issue I am having is that the sheer size of this database, is making every byte count... (40+ million records) And disk space is a cost, which I am trying to work around... -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0e6af7e7-55aa-41c4-99a4-13c27c98f293%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
