skip-group-if-null=

I am having a problem using the attribute "skip-group-if-null" in the group element for my dbschema.

I have a dbschema with 3 required tables and 3 optional tables. In the three optional tables I have skip-group-if-null="yes" so that if there is data it will be deployed, but if there is no data, then the table with null data will be skipped and the deployment will continue.

The deployments don't seem to work this way. If the first table in the list of optional tables fails, then the remaining optional tables are skipped. This is not the expected behavior. In the OpenDeploy Reference guide, the notes on the group element state: "OpenDeploy will skip inserting the corresponding row into the table. OpenDeploy will then continue deploying into the ohter tables in the schema." (pg 192)

Is this a Bug in OpenDeploy/DataDeploy? I am using OpenDeploy 6.0.1 on Teamsite 6.5.

Thanks for any insight.

Find more posts tagged with

Comments

Migrateduser

This is a bug in our documentation. By "continue deploying" it means to continue with deploying the other tuples.The documentation for 6.0.2 now reads:

skip-group-if-null - indicates whether (yes) or not (no) the database deployment should proceed even if a particular tuple cannot be inserted into the table. For example, if the table has a primary key constraint and the tuple value for the primary key is null, OpenDeploy will skip inserting the tuple into the table and in all subsequent tables that are processed. Instead of halting and rolling back the entire deployment, OpenDeploy will continue processing the remaining tuples comprising the deployment.

Note however, that if the tuple was inserted correctly into any tables prior to encountering the problematic table, those earlier processed tables will not be reverted. The tuple will remain in those tables. Specifically, while processing the tuple for the tables comprising the schema, OpenDeploy will only skip insertion once it encounters an error a particular table. Only that table and subsequent tables will get skipped.

Sorry for the confusion.
Mariam

ICMS

How do I implement the situation I describe above? I basically have a set of core tables that all content types write to. I also have a set of specialized tables (one per content type) that I want to write to. I am having trouble finding a way to only write to tables for a particular content type.

For example
DCR 1 should write to Table A and Table B
DCR 2 should write to Table A and Table C.

Any ideas? Thanks for the documentation clarification.

Ottawa_IWOV

Can you identify where in the documentation this is referenced. Exactly what manual and what version number? I can't seem to find it.

TIA,

Lucas

This is a bug in our documentation. By "continue deploying" it means to continue with deploying the other tuples.The documentation for 6.0.2 now reads:

skip-group-if-null - indicates whether (yes) or not (no) the database deployment should proceed even if a particular tuple cannot be inserted into the table. For example, if the table has a primary key constraint and the tuple value for the primary key is null, OpenDeploy will skip inserting the tuple into the table and in all subsequent tables that are processed. Instead of halting and rolling back the entire deployment, OpenDeploy will continue processing the remaining tuples comprising the deployment.

Note however, that if the tuple was inserted correctly into any tables prior to encountering the problematic table, those earlier processed tables will not be reverted. The tuple will remain in those tables. Specifically, while processing the tuple for the tables comprising the schema, OpenDeploy will only skip insertion once it encounters an error a particular table. Only that table and subsequent tables will get skipped.

Sorry for the confusion.
Mariam

Migrateduser

This is doc'ed in the OD Reference Guide where the DTDs are described.

Mariam

Migrateduser

I'm trying to use this option, skip-group-if-null, and it's just not working. I have 3 tables in my deployment and the latter 2 are optional. The error I am receiving is:

NumberFormatException occured while converting [null] for column [contest_question_id]

According to the documentation, if I have set skip-group-if-null to "yes", it should skip this group, no?

I'm referring to OD 6.0.1.

Also, why does there seem to be such little documentation about this and no examples provided with OpenDeploy?

(added later):

I also get the error:

DAS:ERROR:Value(s) for PK column [contest_question_id] missing in [templatedata...(blah blah)]

So, what is this feature for and is there more elaborate documentation *anywhere*?

Migrateduser

Dave,

I think your best bet is to open a support case so we can take a closer look.

Mariam

Migrateduser

Mariam,

Thank you for your quick response. I don't think this particular customer has a support contract with Interwoven but I might open one next week under the guise of another customer :-)

Thanks again,

Dave