nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DataDeploy - can I rollback what I just deployed?

Bill Klish

OD 6.1.1 Patch 2
Solaris 9
MySQL target DB

We are in the process of investigating the conversion of some old Perl code that deploys content to a database in favor of using DataDeploy.

Getting the data into the database is much easier then all of the Perl stuff we had to code. However, I am having a hard time trying to make DataDeploy satisfy the following use case.

If a user successfully deploys content, previews the site and doesn't like what is out there, I don't want to delete the DCR, but rather roll back the database contents. Without deleting the DCR, I am not sure how I can force DataDeploy to remove what was just added. I screwed around with not using the IWDELTRACKER table, but not sure that is what I want to do either.

Is this a product limitation or am I missing something?

Find more posts tagged with

Comments

cute_guy

OD 6.1.1 Patch 2
Solaris 9
MySQL target DB

We are in the process of investigating the conversion of some old Perl code that deploys content to a database in favor of using DataDeploy.

Getting the data into the database is much easier then all of the Perl stuff we had to code. However, I am having a hard time trying to make DataDeploy satisfy the following use case.

If a user successfully deploys content, previews the site and doesn't like what is out there, I don't want to delete the DCR, but rather roll back the database contents. Without deleting the DCR, I am not sure how I can force DataDeploy to remove what was just added. I screwed around with not using the IWDELTRACKER table, but not sure that is what I want to do either.

Is this a product limitation or am I missing something?

Why don't you use editions ?
If current updates is not satisfactory then rollback to the previous edition.

Ambuj

Why don't you use editions ?
If current updates is not satisfactory then rollback to the previous edition.

But will it delete the data from database??

Ambuj

OD 6.1.1 Patch 2
Solaris 9
MySQL target DB

We are in the process of investigating the conversion of some old Perl code that deploys content to a database in favor of using DataDeploy.

Getting the data into the database is much easier then all of the Perl stuff we had to code. However, I am having a hard time trying to make DataDeploy satisfy the following use case.

If a user successfully deploys content, previews the site and doesn't like what is out there, I don't want to delete the DCR, but rather roll back the database contents. Without deleting the DCR, I am not sure how I can force DataDeploy to remove what was just added. I screwed around with not using the IWDELTRACKER table, but not sure that is what I want to do either.

Is this a product limitation or am I missing something?

You can have a delete workflow having an external datadeployment for deleting data from database. If user is not satisfied with the output s/he can invoke this delete workflow.. I'm not sure whether without IWDELTRACKER you can use this "delete" function of datadeploy or not... need some investigation there...

Adam Stoller

OD 6.1.1 Patch 2
Solaris 9
MySQL target DB

We are in the process of investigating the conversion of some old Perl code that deploys content to a database in favor of using DataDeploy.

Getting the data into the database is much easier then all of the Perl stuff we had to code. However, I am having a hard time trying to make DataDeploy satisfy the following use case.

If a user successfully deploys content, previews the site and doesn't like what is out there, I don't want to delete the DCR, but rather roll back the database contents. Without deleting the DCR, I am not sure how I can force DataDeploy to remove what was just added. I screwed around with not using the IWDELTRACKER table, but not sure that is what I want to do either.

Is this a product limitation or am I missing something?

You'd have to deploy a previous version of the DCR with dateDifferent="yes" or revert="yes" to ensure that OD/DD transfers the "old" contents of the DCR.

Bill Klish

Thanks for all the thoughts, but not what I am looking for.

Let's say I push something to a preview environment that has a jsp front end and a db backend. If I am just working with content that is not ready to be seen by others, and want to remove the data from the database (without deleting the DCR, rolling back to some other edition, etc.). I just want to keep the preview environment clean.

Rollback was the wrong term here. I want to keep the contents of the DCR as they are, just want them removed from the database.

Adam Stoller

Thanks for all the thoughts, but not what I am looking for.

Let's say I push something to a preview environment that has a jsp front end and a db backend. If I am just working with content that is not ready to be seen by others, and want to remove the data from the database (without deleting the DCR, rolling back to some other edition, etc.). I just want to keep the preview environment clean.

Rollback was the wrong term here. I want to keep the contents of the DCR as they are, just want them removed from the database.

Frankly I think that would be easier to do not using DD.
To do it with DD you'd have to make DD think you deleted the DCR (move it aside?) so that it might delete the entries in the DB (and then move the DCR back into place?)

If you're writing your own DB interaction code (Perl or Java) you can parse the DCR to find the data you inserted and remove it without pretending to remove the DCR.

Bill Klish

Well as I am now learning, DataDeploy has a hard and fast rule on Sybase that you need to deploy into a case insensitive schema or it fails. Seems like a pretty silly limitation, but an issue that will not be addressed until maybe the next release.

So, back to the drawing board it seems...

kajjubee

Maybe have a dropdown field in the DCR called "State" with values "Live" and "Delete" and write a script in your workflow to manipulate the DD depending on the value selected.