NNTP-Posting-Host: adsl-151-7.wanadoo.be
X-Trace: sinclair.be.wanadoo.com 1074780814 1205098 213.177.151.7 (22 Jan 2004 14:13:34 GMT)
X-Complaints-To: (e-mail address removed)
NNTP-Posting-Date: Thu, 22 Jan 2004 14:13:34 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Path: cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
..phx.gbl!newsfeed00.sul.t-online.de!t-online.de!130.59.10.21.MISMATCH!irazu.
switch.ch!switch.ch!ecngs!feeder.ecngs.de!feed1.news.be.easynet.net!news.be.
wanadoo.com!news.wanadoo.be!not-for-mail
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.compactframework:43734
X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
Basically I wanted to add two (or three) primary keys in a single table. The
main reason for that is that it _should_ be faster to find DataRows using PK
as search keys. In the meantime I just managed to do it without the PK's, I
do the basic select operation. I'm just wondering whether there are any
performance implications when using the Select method instead of the Find
method.
"Ilya Tumanov [MS]" said:
By multiple primary keys, do you mean primary keys in several tables or
primary key, constructed out of several columns?
Actually, you can use DataTable.PrimaryKey property to do both.
It accepts an array of DataColumn so you can construct a complex primary
key.
However, I would advise against using several columns as a primary key.
It's a bad practice from both database design and performance point of view.
Consider adding surrogate primary key column.
Best regards,
Ilya
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "jez" <
[email protected]>
Newsgroups: microsoft.public.dotnet.framework.compactframework
Subject: Re: XML DataSet schema
Date: Wed, 21 Jan 2004 08:50:41 +0100
Organization: Wanadoo Belgium
Lines: 175
Message-ID: <
[email protected]>
References: <
[email protected]>
<#
[email protected]>
NNTP-Posting-Host: adsl-151-7.wanadoo.be
X-Trace: sinclair.be.wanadoo.com 1074671460 1161516 213.177.151.7 (21
Jan
2004 07:51:00 GMT)
X-Complaints-To: (e-mail address removed)
NNTP-Posting-Date: Wed, 21 Jan 2004 07:51:00 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!npeer.de.kpn-eurorings.net!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed.arcor-online.net!feed1.news.be.easynet.net!ne then
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor-online.net!feed1.news.be.easynet.net!news.be.wanadoo.com!news.wanadoo.be!not-for-mai schema
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGXS01.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!130.5910.21.MISMATCH!irazu.switch.ch!switch.ch!solnet.ch!solnet.ch!newsfeed.tiscali.ch!feed1.news.be.easynet.net!news.be.wanadoo.com!news.wanadoo.be!not-for-
new
item encountered
the dataset,
the