File deletion and datadeploy

I would like to set a flag in our DB to 'inactive' for deleted content through a standalone datadeployment invoked upon submission of a deleted file - i.e. I don't want the actual record associated witht the file or dcr to be removed from the DB, I just want to change a column value if the file has been deleted. Is this possible? Using OD 6.1, TS 6.5 on Win 2003. Thanks!

Find more posts tagged with

Comments

Adam Stoller

I would like to set a flag in our DB to 'inactive' for deleted content through a standalone datadeployment invoked upon submission of a deleted file - i.e. I don't want the actual record associated witht the file or dcr to be removed from the DB, I just want to change a column value if the file has been deleted. Is this possible? Using OD 6.1, TS 6.5 on Win 2003. Thanks!

You might be able to do this with a tuple preprocessor, or using Perl DBI (or Java equivalent) instead of DD - or you could go through some elaborate deletion process that first sets a value for some field to "inactive" deploys that, then deletes the DCR and submits and does not deploy the DCR to the DB again. Or perhaps just set some value in the DCR to "inactive" and does not delete the DCR, but use FormAPI in the DCT to set all fields (other than the one marked "inactive" to read-only if that field is marked "inactive" -- but then you'd never be deleting the DCRs except when you want the entries to be removed from the DB.

It's basically a matter of determining your actual requirements and coming up with a design that makes sense to support them, or determining that the requirements as specified do not make sense and that the requirements need to change so that they do make sense.

Migrateduser

I would like to set a flag in our DB to 'inactive' for deleted content through a standalone datadeployment invoked upon submission of a deleted file - i.e. I don't want the actual record associated witht the file or dcr to be removed from the DB, I just want to change a column value if the file has been deleted. Is this possible? Using OD 6.1, TS 6.5 on Win 2003. Thanks!

I have not really found any desireable reason to delete the DCR from TeamSite, but leave the orphaned record in the DB.. actually, that situation has sometimes cause me great headaches when something was wrong in the DD config (like incorrectly setting the foreign keys, etc) and it leaves orphans in some tables and then subsequent deploys fail...

I usually have an active/inactive radio button (as Ghoti suggests) in my DCT's in this situation for this purpose so users can "deactivate" content without it being removed from the DB. if your just trying to maintain some list of deleted stuff, you can also do a trigger or something on one of the tables that can store some value on delete of the record.. it would need some logic in it since DD (with real-updates not on) will delete and reinsert the record on redeploy, but that all goes back to what your real requirements are and how to solve the actual "problem" or meet the desired outcome..

Assia

The reason for this requirement is that we need file deletions to trigger re-indexing through a custom search application we have developed, and because we dynamically embed content from our teamsite-generated files in our call center knowledge-base application. So, if something is deleted, our application notifies a KB specialist to revisit the content. Anyways - what you suggested seems to be the most straightforward thing to do - implement a trigger in the Oracle db directly.

Thanks a million.

Migrateduser

The reason for this requirement is that we need file deletions to trigger re-indexing through a custom search application we have developed, and because we dynamically embed content from our teamsite-generated files in our call center knowledge-base application. So, if something is deleted, our application notifies a KB specialist to revisit the content. Anyways - what you suggested seems to be the most straightforward thing to do - implement a trigger in the Oracle db directly.

Thanks a million.

just keep in mind with a delete trigger, if your dataDeploy is not set to real-updates (which I tend to have issues with sometimes when it is, so I usually leave it off), every insert comes after it does a delete.. so your delete triggers will get fired off for every file pushed, updated or deleted... so the script that does the re-index should probably do a look first to see if the delete record actually exisits in the other table (i.e. was not a real delete, was actually an update).. I had to something similar with FAST.