ChangeLog 3.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192
  1. 2006-11-28 Nagappan A <[email protected]>
  2. * XmlDataDocument.cs (StringToObject): Modify
  3. XmlConvert.ToDateTime to use XmlDateTimeSerializationMode, as the
  4. default ToDataTime method id obsolete.
  5. 2006-04-19 Senganal T <[email protected]>
  6. * XmlDataDocument.cs :
  7. - Use encoded names for DataSet schema.
  8. - StringToElement : Return 'null' if the value is empty string
  9. or null.
  10. - OnDataTableRowAdded : Add the row elements to the tablenode if
  11. they are not already added.
  12. 2004-06-06 Atsushi Enomoto <[email protected]>
  13. * XmlDataDocument.cs :
  14. - It was not handling SimpleContent. This fixes bug #56951.
  15. - It was not converting values into DataType of the DataColumn.
  16. 2004-05-17 Atsushi Enomoto <[email protected]>
  17. * XmlDataDocument.cs :
  18. Removed MonoTODO from implemented members and private members.
  19. Updated OnNodeRemoved(), OnDataRowDeleted() and OnDataTableRollback()
  20. to match with current implementation.
  21. 2004-05-13 Atsushi Enomoto <[email protected]>
  22. * XmlDataDocument.cs : Removed row-element mapping. Just use new
  23. DataRow.DataElement property. Added/removed some comments.
  24. 2004-05-12 Atsushi Enomoto <[email protected]>
  25. * XmlDataDocument.cs : Radical design change.
  26. - GetElementFromRow() must return "detached" element, even if it is
  27. not added to table's Rows.
  28. - Introduced XmlDataElement class to map element (this class itself)
  29. and DataRow _always_ . It is impossible to map *all* DataRows
  30. to/from elements only in XmlDataDocument API, since DataRow can
  31. be created separate from it (i.e. by table.NewRow()).
  32. - Removed unreliable GetElementsByTagName() dependency from most
  33. of the code, since users might create elements that has the same
  34. name of any tables (that is possible especially unmapped elements).
  35. - Adding/Removing delegates on every event action is unnecessary.
  36. Use just flags.
  37. - For Load(), just using base.Load() will do most of the job.
  38. - Attributes and SimpleContents are not handled properly.
  39. "Removed" and "Rollback" events are still TODO.
  40. 2004-04-13 Atsushi Enomoto <[email protected]>
  41. * XmlDataDocument.cs:
  42. Load() should not read xml multiple time nor expect BaseURI (and it
  43. indicates the resource location is readable).
  44. Simplified event handling logic, and fixed missing event removal.
  45. Quick hack to avoid new XmlDataDocument(DataSet ds).Load ().
  46. Enabled CreateNavigator() that was commented out.
  47. 2004-03-18 Atsushi Enomoto <[email protected]>
  48. * XmlDataDocument.cs : Fixed incorrect cast in OnDataTableRowAdded().
  49. This fixes bug #54505.
  50. 2003-07-31 Duncan Mak <[email protected]>
  51. * XmlDataDocument.cs (BaseURI):
  52. (InnerXml):
  53. (IsReadOnly):
  54. (this):
  55. (LocalName):
  56. (Name):
  57. (OwnerDocument):
  58. (WriteContentTo):
  59. (WriteTo): Removed, these do not need to be redefined, as
  60. they are inherited from XmlDocument already.
  61. (CreateElement): simplifed the
  62. implementation. XmlDocument.CreateElement can handle String.Empty
  63. and null just fine.
  64. 2003-03-12 Alan Tam <[email protected]>
  65. * XmlDataDocument.cs: Still need to print tag for the DataSet if there
  66. is no data at all.
  67. 2003-01-27 Ville Palo <[email protected]>
  68. * ChangeLog: Added this file.
  69. * XmlDataDocument.cs: Some little fixes.