I thought that it would be useful to keep role histories in these
entities, but didn't realized that it will modify the primary keys and
makes it PITA.
I will give up(for now).
Thanks for your help guys.
Bilgin
+1
On Thu, Jul 17, 2008 at 1:58 PM, Jacopo Cappellato
[EMAIL PROTECTED] wrote:
Hi Bilgin ,
from/thru dates (with from date in the primary key) are useful when you
have to record the history of roles associated to an entity (e.g. who was
the administrator of the product store in 2004?).
Jacopo, Adrian, Ashish, thanks for your comments.
Then I'd like to propose the following changes:
Add fromDate - thruDate fields to following entities:
ProductStoreGroupRole
FacilityGroupRole
FacilityRole
AgreementRole
MarketingCampaignRole
SegmentGroupRole
Remove fromDate - thruDate fields to
On Jul 18, 2008, at 11:13 AM, Bilgin Ibryam wrote:
Jacopo, Adrian, Ashish, thanks for your comments.
Then I'd like to propose the following changes:
Add fromDate - thruDate fields to following entities:
ProductStoreGroupRole
FacilityGroupRole
FacilityRole
AgreementRole
MarketingCampaignRole
On Jul 18, 2008, at 3:23 AM, Jacopo Cappellato wrote:
On Jul 18, 2008, at 11:13 AM, Bilgin Ibryam wrote:
Jacopo, Adrian, Ashish, thanks for your comments.
Then I'd like to propose the following changes:
Add fromDate - thruDate fields to following entities:
ProductStoreGroupRole
Hi Bilgin ,
from/thru dates (with from date in the primary key) are useful when
you have to record the history of roles associated to an entity (e.g.
who was the administrator of the product store in 2004?).
That said, ProductStoreRole, ProductStoreGroupRole, FacilityGroupRole
seem all
I agree with Jacopo. From/Thru dates should be used in entities that are
expected to keep historical data.
-Adrian
Jacopo Cappellato wrote:
Hi Bilgin ,
from/thru dates (with from date in the primary key) are useful when you
have to record the history of roles associated to an entity (e.g.
