blab | gem allows to trace local variables | Code Inspection library

You haven't mentioned if you have any indexes on table B. Perhaps an index on it with the identifier and 'including' any columns you want to output.

Now, from what I gather in the comments, you're really joining to tables b and c primarily as a filter, not because you need to output data from those tables. If that's really the case, you should use exists. You may shy away from subqueries, but the engine knows what to do with exists. You'll see in the plan that it will run a 'semi join'.

You can use

I suspect you're not trying to merge on actual dates but a month so you're using a formatted value most likely. So set your dates to the beginning of the month or convert them to YYMM to merge.

Try

Try doing this inside your out() function

The root of the issue is that your Config struct is incorrectly structured.

I recommend using json-to-go when converting JSON to Go structs; this tool will help you catch issues like this in the future.

Once you get your struct constructed correctly, you'll also notice that your struct fields are not capitalized, meaning they will not be exported (i.e. able to be used by other packages), which is another reason that your UnmarshalMap code will not return the result you are expecting.

Here is a good answer on struct field visibility and its importance, briefly summarized above.

Below is a corrected version of your struct that, combined with your UnmarshalMap code, will correctly allow you to print your item and not receive a {} which is no fun.

It is not a nodemailer error

I fix my problem adding a missing configuration in my gmail account YOUR_EMAIL_ADDRESS "Gmail Send Mail As"

You could review how to add "Gmail Send Mail As" in:

https://www.youtube.com/watch?v=8Esd85pyH8I&feature=emb_logo&ab_channel=GoldyArora

Following the instructions in https://medium.com/@imre_7961/nodemailer-with-g-suite-oauth2-4c86049f778a

I confirm that the writing by Bogdan Bota works and I was able to send emails from a group email in my organization info@domain.com validating from my account cesarcas@domain.com.

Also note that you need to have access to group email, in mi case, info@domain.com to be able to validate that you can use that address to send emails.

It is possible, but cumbersome, you must implement your own ICSharpEntityTypeGenerator and hook that into the Scaffold command via a design time factory.

Alternatively, if I understand your requirement, you would like to avoid all data annotations, except [Key], is that correct? In that case, it may be something I can implement in EF Core Power Tools. Feel free to post a feature request on GitHub.

You should deploy first and then run your e-2-e tests but not on production. On production you should run smoke tests which are kind of e-2-e tests which test crucial parts of your app without changing state of the app. (of course it makes sense to run them after deployment)

So it could be in high-level like this: