Typed Datasets
-
Hi, Can anyone let me know if the usage of typed datasets in ADO.NET has any serious limitations compared to untyped datasets ? Thanks in advance, Kanchana
Usually it's untyped datasets that are considered more limited than typed ones, unless you are accessing data you know little about. However, it really depends on what you want to do. Typed datasets essentially just means the types are known and understood, whereas untyped ones are generic, and hence less is known (and needs to be known). Typed sets are much more efficient, since more work is done at compile time than at runtime. Also, typed sets can do more error checking to avoid mistakes. Commonly, the goal is to use typed sets whenever possible. Untyped sets can be a little simpler at first, since less needs to be specified, column names do not need to be known, etc. If you do need to work with untyped sets at some point, it's useful if you can have a schema automatically generated, so you can move to typed sets. That will depend on the situation, though. If you do not consider needing to know what types to deal with to be a problem, then I cannot think of any serious limitations with typed datasets. Cheers