>>>>> On Wed, 29 Jun 2011 22:40:16 +0100, Gavin McCullagh said: > > The database was originally made in Ubuntu Hardy which was v2.x as I recall > now. We then upgraded to v3 (ubuntu packages built using the debian > package git archive as we needed volume shadow copy support under Win64) > and since then moved to v5 using the Lucid packages. > > So, yes, made by old versions. Am I missing a constraint I should have?
No, the current MySQL table definitions don't have that constraint either. I think Bacula has very few constraints for performance reasons. I was wondering about old versions because that increases the chance that a bug in Bacula caused it long ago. Bacula's dbcheck program has an option to eliminate the duplicates, which suggests that it was a problem at some time in the past. __Martin ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
