DumpData: avoid IOException with unclosed StreamWriters
after an exception gets thrown in the data dump, there is a sharing violation on _row_count.txt
datadump: parse commitment dates in correct format.
in fulldump23.p, we define dmy as format for the dates.
This needs to be specified when parsing the date in the converter routines for Partner.GiftDestination.
make sure that the exception handler does not throw the error again...
for debugging: keep fulldump/*.sql.gz files, and only delete the ones that you want to convert again.
otherwise all tables will be upgraded again.
calling with -clean parameter will delete all sql.gz files before doing the upgrade.
datadump for Petra 2.x: increase speed of PopulatePPartnerGiftDestination
using a sortedlist instead of listing the csv strings, which are compared in every search run.
datadump from Petra 2.x: consider family id when calculating gift destination
Datadump from Petra 2.x: fix problem with a_form_element
check if we have multiple rows with same formcode and formname, with sequence 0
if patch 2.2.7 has been run, we should already have valid sequences
datadump from Petra 2.x: first convert the data from parsed tables, before using them for writing.
otherwise the date format will not work for postgresql load.
solves a problem for table pm_person_skill, date created and date modified.
datadump from Petra 2.x: new parameter create_test_files
it defaults to true.
if it is set to false, no test.sql.gz files are written.
they are only needed for validation and debugging
datadump: another fix for partner gift destination: format dates properly for postgresql
resolve some mix up with PersonQualification and PersonAbility
merge from lp:~tpokorra/openpetraorg/20140626_upgradePetra2