[SCHEDULER-865]  Importing Database is Fragile
Type Bug
Priority Low
Severity Trivial
Component Database Access Component
Fixed In Version [3.6] 3.6
Versions Affected [3.5.3] 3.5.3
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 10/22/2013

Description 
The logic for importing a database from exported XML is fragile. it will get lost if it encounters an empty element like <Description></Description> (and I don't know what it will do with <Description />). It currently depends on the exporter avoiding inclusion of empty elements, but this is flaky. The import logic (and it is in all of the classes in Database.cs) should be able to recognize empty elements and just deal with them. This would apply to text and memo columns...

Comments
10/22/2013 5:10:25 PM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

  Repository
  svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 

 

  SVN Revision
  312
 

 

  Affected files
  /trunk/Database/Database.cs (Modified)
/trunk/Help/RelNotes.htm (Modified)

 

 

  Check-in comment
  Multiple database export/import problems.
GEM:865
10/22/2013 4:58:21 PM   Bob Denny 
Short form of empty is really evil on import. The empty element also is evil. Why? In any case, detect whitespace in these things and do not piutput empty elements in the exports. This applies all over the place.