jobd | Jobd implements cron as a 9p file system | Continuous Deployment library

because you use commit=False, is that not save the instance into db.

This save() method accepts an optional commit keyword argument, which accepts either True or False. If you call save() with commit=False, then it will return an object that hasn’t yet been saved to the database. In this case, it’s up to you to call save() on the resulting model instance. This is useful if you want to do custom processing on the object before saving it, or if you want to use one of the specialized model saving options. commit is True by default.

Another side effect of using commit=False is seen when your model has a many-to-many relation with another model. If your model has a many-to-many relation and you specify commit=False when you save a form, Django cannot immediately save the form data for the many-to-many relation. This is because it isn’t possible to save many-to-many data for an instance until the instance exists in the database.

To work around this problem, every time you save a form using commit=False, Django adds a save_m2m() method to your ModelForm subclass. After you’ve manually saved the instance produced by the form, you can invoke save_m2m() to save the many-to-many form data.

you can see this from the documentation :

https://docs.djangoproject.com/en/3.2/topics/forms/modelforms/#the-save-method

Your sendMail does not return a Promise, then await keyword will not work as your expectation. The function will be finished before the sendMail process finish.

On the local side, I guess you use serverless-offline plugin to test your function. Then, the function will not "finished", it just responds -> Different behavior with Lambda environment.

If this.transporter is an instance of Nodemailler's Transporter, then .sendMail function is a callback function. You have to convert it to a new function that returns a Promise or just wrap it into a new Promise like this:

You can use the --parsable option to get the jobid of the previously submitted job:

To be able to use left join in hql you should correct your mapping for Person in the following way:

I tried your code, and I put %SIZE(USRI00300) as the second parameter, and I got zero for suppGrpIdx too.

As Charles and Mark Sanderson implied, you have to make the receiver big enough to give all the information and also tell the API how big the receiver is. I'm guessing that since you defined your data structure as based, that you are setting p_usrData to some larger storage. If so, give the length of the larger storage instead of the size of USRI0300.

When I set p_usrData to point to a 32767-length buffer, and put %size(buffer) as the second parameter, I got 722 for suppGrpIdx.

In the end of the SQL statement you left a single quotation mark. Try to fix it first and if it will not help, then print the SQL and try to insert it manually to MySQL, it should show what is wrong.

You should include NULL value as a valid value of bat field in the select sentence.

This will solve your problem.

One option involving dplyr and purrr could be: