DataSet feature requests

We have begun the initial planning for the next version of the DataSet (post VS 2005). If you have a feature you would like to see, let me know.

I can also pass on feature requests for other components in System.Xml and ADO.net to the proper folks.

Comments

• Anonymous
  February 28, 2005
  A pattern or feature that supports multilevel Undo.
  
  (1) I want to use a (possibly disconnected) DataSet to hold the state of my application.
  
  (2)Any modern app must have multi-level undo.
  
  It would be a HUGE help if there were some kind of journalling/checkpoint/transactional function in the DataSet that could be used to implement multilevel undo.
  
  
  (If there's already a good way to do it, then PLEASE while you're in a planning cycle try to plan some time for someone to write about how to do this because patterns for implementing multilevel undo apps in the .NET framework have not been effectively communicated and evangelised into the community)
  
  -Don
• Anonymous
  February 28, 2005
  The comment has been removed
• Anonymous
  February 28, 2005
  produce xsd schema that validates the xml instance
• Anonymous
  February 28, 2005
  Bring back paging support that was removed from Whidbey! This was a huge mistake to remove in my humble opinion
• Anonymous
  February 28, 2005
  I'd like to see automatic saving of master-detail dataset relationships inside a transaction.
• Anonymous
  February 28, 2005
  My suggestions are right here --
  http://codebetter.com/blogs/sahil.malik/archive/2005/02/28/56200.aspx
  
  Hope-u-like-'em !!
• Anonymous
  February 28, 2005
  The comment has been removed
• Anonymous
  February 28, 2005
  Allow to set the RowState of a Row Manually. Thnx :-)
• Anonymous
  February 28, 2005
  Please provide a sort method that can help us sort the original data in a dataTable. I don't like use the sort method in DataView:)
• Anonymous
  March 01, 2005
  Yes. Multi-level undo would be cool.
  
  If the COmega data/sql ideas land in the platform, it would be great if we could use the dataset with this.
• Anonymous
  March 01, 2005
  Andrew,
  
  I have quite a few good participating comments on my blog entry with a few good suggestions there too.
  
  http://codebetter.com/blogs/sahil.malik/archive/2005/02/28/56200.aspx
  
  - SM
• Anonymous
  March 01, 2005
  We're working hard with DataSets for the last 3 years and we missed some features:
  
  - Don't mark ColumnName as internal. We have all of them in a shared Assembly, because we use the typed DataSets on Client and Server.
  
  - Default value and maxlen and foreign key constraints should be read from the database.
  
  - We miss a general update mechanism of typed DataSets when the database has changed .
  
  - In case of a constraint error, it would be nice to add the column and the type of error in the exception message.
  
  - We trapped a lot of times in the deleted Row pitfall, while accessing the row.
  
  - We wrote some utility methods to :
  - fill default values into a new row
  - copy a row into another dataset
  - copy the whole dataset into another one
  - initialize the dataset's increment and seed to negativ for newly added rows
  - create a table copy of a view
  - add or remove additional filters to a view
  - get the names of columns with changed values
  - ask whether a column has changed values
  
  contact me through thomas.weingartnerATgmx.ch
• Anonymous
  March 01, 2005
  How about the ability to have one datatable definition, but have it included in many datasets? For example I have a Notes table that is referenced in many other tables - I should be able to create one Note DataTable Type and have it contained in multiple DataSets.
• Anonymous
  March 03, 2005
  Have an option to deleted rows as normal rows. I want to iterate over all the rows and ask for the rowstate, and access the values as if they were normal rows. Accessing deleted rows today is a pain
  
  - I want to do a .Find() by any unique key.
  
  - When I have master/detail tables I want to set as 'Modified' the parent when I modify the childs. This is because I need to validate the whole entity when something changed in it, and to know if something changed I need to traverse all the child rows to ask that.
  
  
  
  
• Anonymous
  March 04, 2005
  The comment has been removed
• Anonymous
  March 08, 2005
  Surely n.1: allowing (filtered) joins. If you have two datatables and a relation, you should have a way to do joins (other than the simplistic getchildrecords).
  example: I have a CookieType and a Cookie table.
  If I want all the cookies that are of a given type, it's easy, but let's say I want to know all the types of cookies for the coookies where cookie.price==5.
  That would be nice!
  n.2: Faster and smarter merge.
  hope it helps.
  m.
• Anonymous
  March 09, 2005
  XSLT processor which optimizes applying templates when multiple templates have similiar match with the same priority, for instance differfence in value of an attribute
• Anonymous
  March 12, 2005
  Please nix the DataSet from the framework entirely
  
  <-- I don't advocate that for multiple reasons.
• Anonymous
  March 15, 2005
  The comment has been removed
• Anonymous
  March 17, 2005
  I would like a method that creates a DataView and a new DataTable based on two or more related datatables. I would like it to behave exactly like a SQL Join Statement.