m...@kitchenpc.com (Mike Christensen) writes:
I have a table that stores a user ID and a subscription type, and this is
really all it needs to store and any pair of values will always be unique. In
fact, I think this pair should be the primary key on the table. However, I'm
using Castle
I have a table that stores a user ID and a subscription type, and this is
really all it needs to store and any pair of values will always be unique.
In fact, I think this pair should be the primary key on the table. However,
I'm using Castle ActiveRecord which says at:
On Sat, May 1, 2010 at 8:25 PM, Mike Christensen m...@kitchenpc.com wrote:
I have a table that stores a user ID and a subscription type, and this is
really all it needs to store and any pair of values will always be unique.
In fact, I think this pair should be the primary key on the table.
On May 1, 2010, at 7:25 PM, Mike Christensen wrote:
\And I quote:
Quick Note: Composite keys are highly discouraged. Use only when you
have no other alternative.
I get the feeling they're discouraged from a SQL point of view, but
it doesn't actually say why anywhere. Is there any good
On Sat, 2010-05-01 at 19:25 -0700, Mike Christensen wrote:
--I have a table that stores a user ID and a subscription type, and this
is really all it needs to store and any pair of values will always be unique.
In fact, I think this pair should be the primary key on the table. However, I'm
