don't require test user to have access to mysql database
clarify test instructions
fix TestDistributedIds for case-sensitive databases
target -> .gitignore
logging org.hibernate at INFO causes spam
Merge pull request #3 from pimlott/master

Random cleanups
Lazily compute fingerprints in TM3Tuv

    TM3Tuv.setContent() used to immediately calculate the fingerprint
    on the underlying data object, even if it was never used.  This is
    now done lazily.
remove unneeded executable modes
fix javadoc warnings
clarify lookup docs, param names

- Renamed sourceLocale -> keyLocale, to emphasize that it's the source of
  the matchKey param, not the matched TU.  (This was already done in
  FuzzyIndex methods.)
- Rename targetLocales -> matchLocales, to emphasize that they don't
  necessarily need to be target locales of the match.
- Make the javadoc more explicit, especially about lookupTarget
fix fuzzy lookup on bilingual TMs

lookupTarget was taken to mean _only_ target in 42b750e, which is not the
intent.  This made testFuzzyLookupTargetOnlySearchesTargets pass, but not
for the right reason.  In fact, the test was failing because bilingual fuzzy
search was not taking keyLocale into account, so would find "A" in a
different locale.

This commit reverts 42b750e, takes keyLocale into account, and makes the
test more thorough regarding keyLocale and lookupTarget (and changes the
name).
Merge pull request #6 from pimlott/master

Fixes from today.
repeat testDataByLocaleOrdering with different save methods

- Factor out the save method into interface SaveMethod.
- Introduce testDataByLocaleOrderingFlushTus (identical to the old
  testDataByLocaleOrdering) and testDataByLocaleOrderingSaveMultiple.
- Add a code commenton clarifying why testDataByLocaleOrderingSaveMultiple
  works.
handy fuzz matching test data
use fuzzy test data in testFuzzyLookupKeyLocaleAndLookupTarget
testBadLocale for BilingualTm

Obviously this test should fail early, but amazingly it all passes!  I added
an exception and structured it as an "expected fail" (which JUnit doesn't
realy have) to try to make this clear.
doc tweak
Merge pull request #8 from pimlott/master

More tests, a little doc.
use non-identity-affecting attributes in exact matches

Previously, implementations of getExactMatchStatement were filtering them
out (in contrast to implementations of getFuzzyLookupQuery).  This is
probably because findTuForSave doesn't want to search on them.  But
findTuForSave should take care of that itself.

Test included.
Merge pull request #9 from pimlott/master

Something I discovered affecting TDA