Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
DataDeploy Issue
dlsoderberg
I have a DCT that we're using to deploy content to 2 tables. The first table is populating correctly, but the second table is not updating. My first table, ARTICLE, has a primary key of ASSET_ID. My second table, CONTENT_MEDIA, has a foreign key of ASSET_ID from the ARTICLE table. CONTENT_MEDIA has no primary key...just 2 foreign keys and a check that ASSET_ID is not null. If I set up, the dd config with a primary key, the deploy completes but only updates the ARTICLE table. If I remove the primary key and put in just a foreign key for the CONTENT_MEDIA table, the deploy fails. I'm assuming that I must have something wrong in the dd config, but I haven't used DD all that much and just want to see what some of you more "seasoned" DD people think. I've attached my dd config for review.
Find more posts tagged with
Comments
nakumar
The group/table CONTENT_MEDIA doesn't have a primary key that's why the deployment got failed. DD always expects a primary key for a group/table since querying will be fast enough.
dlsoderberg
I should have mentioned that I have switched it between trying with the primary key being there as well and it doesn't change the outcome of the deploy...nothing updates in the CONTENT_MEDIA table.
nakumar
So, you have defined primary key for both the tables ARTICLE and CONTENT_MEDIA and also foreign key defined in CONTENT_MEDIA right. Can you post the log "src.ddconfig.article*.log" ?
dlsoderberg
Here is the OD/DD log file.
nakumar
From the log, it is clear that you are performing "real update"
DBD: Performing Real Update
DBD: TTableSchemaHelper object for [ARTICLE] found in cache.
But in the config file, "enforce-ri=yes". We can't perform real update when enforce ri is enabled. Please see ddadmin guide to know more on "Real updates"
dlsoderberg
Thanks. I read up on real updates and changed my config to enforce-ri='no'. This did not affect the outcome of the deploy, however.
Bhargav Coca
Try something like this. Please see the attached modified config file for your scenario.
Thanks