When using dbloader it doesn't acknowledge skip-group-if-null

Does anyone know why it is not skipping the insert when there is in fact a null? My code is attached.

thanks :

Find more posts tagged with

Comments

Does anyone know why it is not skipping the insert when there is in fact a null? My code is attached.

thanks :

can you post the full config.. that looks like only part of it.. where are the other groups?

just in case it's an issue of the poorly documented feature on IWOV's part.. this is from the manual and I will take a moment to explain it:

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.

So it almost should be called.. dont-fail-if-null.. because it does not just skip over that Group and go to the next one.. it actually stops proccessing that DCR alltogether... but because of that flag, it doesnt fail your deployment and will continue with the NEXT dcr (or next step of the Workflow, however your deployment is setup)..

Now assuming that part was clear, and your deployment are still failing, the other part that is required is that your skip-group-if-null="yes" group has a foreign-key reference in the config back to the your root-group (whatever group is set to root-group="yes", which can obviously only be 1 group). If you dont have that foreign key set back to that root-group, then the skip-group-if-null="yes" is just ignored (and there probably some questions about the way the config is setup to being with)..

not having enough info about your issue, this may all be useless information to you, but figured since it originally took me a while to get this topic straight, thought it was worth posting.

barnettech

So if it encounters a null while inserting into a table, subsequent tables are not inserted into (processed) either!?!? It just stops processing the dcr? Is there something that lets just the one insert into a table fail, and then subsequent tables and the rest of the dcr still gets processed?

Migrateduser

So if it encounters a null while inserting into a table, subsequent tables are not inserted into (processed) either!?!? It just stops processing the dcr? Is there something that lets just the one insert into a table fail, and then subsequent tables and the rest of the dcr still gets processed?

you are correct in your above statement.. "if it encounters a null while inserting into a table, subsequent tables are not inserted into (processed) either"

if you post your full config, I am happy to take a look at it.. becuase depending on how your order the groups in your config, you can sometimes make it work.. in some of my cases for example, this is exactly what I want it to do.. so for example, if there are just a few groups.. and this one is the only one like that, just put it as the last group, and you should not have an issue.

barnettech

Thank you very much for your replies. The problem is that there are multiple groups involved that may or not be null. It looks like the answer is you have to put dummy values into each table so the rest of the tables get processed. And then your application must be setup to just ignore the dummy values.

Migrateduser

Thank you very much for your replies. The problem is that there are multiple groups involved that may or not be null. It looks like the answer is you have to put dummy values into each table so the rest of the tables get processed. And then your application must be setup to just ignore the dummy values.

I would personally not put dummy values in, but that's just me.. I try to keep the DB as clean as possible.. once you start with dummy values, you then start needing to have your DCT remove them so the user does not see them, and stuff like that.. it ends up being more code to support and produces bad data.

there are other options, as I said, like grouping the ones that will have no value together.. so then if one fails (is skipped), anything after that group can be skipped as well (depending on your data model).

There is also, if I remember correctly, a workaround where you can tell the item within a group it is a replicant [of 1] (even though it's not), and then if its null, it would skip over it and continue to process the DCR.. but again, without any config, I can't really help.