Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (herse.apache.org: domain of siberian@gmail.com designates
 64.233.162.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=giIClOeu7usAT+xNz9M2XBg6kQd6JUdWsmD6s+w/ygwdonuKuoSiKdxDLfSMLXTJHDqyhUbuuI1L1HuM0GM8h7i5GguAFCPO9MURaoIfDkRK2JsDeXCRThOb+HX6lVvHryx44VBsh67pfzgYSwu5SCfjD2Psfzgb+mme9e2G1HA=
Message-ID: <36e916ee0706032309k7cc2d43aifda8aef90923e545@mail.gmail.com>
Date: Sun, 3 Jun 2007 23:09:50 -0700
From: "John Armstrong" <siberian@gmail.com>
To: user@cayenne.apache.org
Subject: Creating Compound PKs
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Does Cayenne allow for the creation of a compound PK? I searched the
archives and google more generally and could only find hints at this.
The docs did not clarify either (although it was also hinted at. .I
think, its a bit late :) ).

My table looks like this:

id
name
serverid
status
enabled

I need to create a compound PK on name/serverid that will maintain
uniqueness across these segments.

My fallback is to create a validation that checks these before commit
but my normal route in a non-ORM context is to let the DB enforce it
and catch it there.

Thanks!
John-