Viewing 8 posts - 1 through 8 (of 8 total)
Thanks for the reply Scott.
The 2 fields are reside in the Deals table for 2 different reasons. Please excuse the terminology, Im no expert but the DealFamily allows a "is-a"...
May 29, 2012 at 2:15 pm
Checked it out, not quite there.
I'll try to explain a little more.
A deal always has one dealtypeId.
A deal can be one of 3 variants - an Offer, a Product or...
May 29, 2012 at 9:49 am
Lowell (5/29/2012)
can't see a reason for the calculated persistent column;
Hi, thanks for the reply, I'm in the process of checking it out.
The reason for the persisted column is this;
Table1:...
May 29, 2012 at 9:31 am
I guess, the initial posting does look rather complicated.
Here's a simpler explanation of what I'm trying to achieve - hopfully.
Table 1: Deals (PK DealId)
DealId int
DealTypeId int
Table 2: DealEvents (PK...
May 29, 2012 at 8:27 am
Sean Lange (5/29/2012)
May 29, 2012 at 8:01 am
Thanks for your advice guys.
I am coding a website for my own business. At the moment I have to be a jack of all trades, and I'm certainly a master...
April 14, 2012 at 3:17 am
Vinu512 is on the right track, and there are ways that you can set up these tables better to resolve your issue, but a better understanding of the scenario would...
April 14, 2012 at 3:13 am
Thanks for the reply.
Splitting the table into 3 won't resolve the issue.
The problem is that I don't have a table keyed StoreId/CategoryId so I've nothing to constrain against.
April 13, 2012 at 7:24 am
Viewing 8 posts - 1 through 8 (of 8 total)