Re: DataRelations vs Joins
From: Kenneth Allen (kendrhyd_at_sympatico.ca)
Date: 12/18/04
- Next message: Justin Echternach: "Re: Detect Window Minimize and Maximize"
- Previous message: Pete Davis: "Re: Security of Obfuscators"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 18 Dec 2004 09:12:23 -0500
Another consideration is whether or not the data will require the
ability to be modified and updated back into the database using the
Update() call on a DataAdapter - in that case a relation is also
recommended. If you want to code any update logic yourself, then the
JOIN can be used.
Note that the use of a JOIN does not eliminate the ability to do any
updates back into the database via an adapter, but it does make the
coding more challenging and you will need to include more control
columns in the JOIN itself.
-ken
Nicholas Paldino [.NET/C# MVP] wrote:
> Phil,
>
> It depends on what your needs are. If you have a need for a
> parent/child relationship in your UI (you have to display it as such), then
> a DataRelation is the way to go, as the responsibility of handling that
> related data is handled by the classes that handle data binding, and not by
> you.
>
> However, if you just need to display this in one place, and no need for
> a parent/child display, (where the child records are shown independent of
> the parent), then I would do the join on the server and return that.
>
> Hope this helps.
>
>
- Next message: Justin Echternach: "Re: Detect Window Minimize and Maximize"
- Previous message: Pete Davis: "Re: Security of Obfuscators"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|