sqlmapper | sqlmapper is a light mapper between go-struct | SQL Database library

It seems there are (seemingly unwritten as I can't find anything online) rules pertaining to the SQL statement that I found when trying to figure this out:

1. The column(s) you specify to split upon cannot be the first column(s) in the SELECT statement
2. Any columns listed AFTER your split column(s) will not be mapped

Simply moving my DateTime column above the split column(s) in my SELECT statement resolved the issue.

According to mapper [NpgsqlValue] cannot be changed from type [date] to [ObjectMapper] to solve the described problem I have 2 options:

1. Remove Exception's details from my log by deleting "WithExceptionDetails" from config file and wait for Postgres exceptions' destructurer to appear.
2. Write custom destructurer.

The error here is using a static - and therefore shared - connection (even though it isn't shown, we can assume that _oracleConnection is static because it is accessed from the static method GetConnection).

Connections are not thread-safe, and by making it static, all your code is sharing a single connection. This tends to scale to exactly one user, i.e. one concurrent request - above that: failure is pretty much guaranteed.

Connections should be scoped for a logical piece of code - which could be anywhere between "a single method" to "an entire request", but they must only be accessed by one thread at a time. You should also ensure that connections are correctly disposed as they leave that scope, to prevent leaking connections.

(BTW: the problem isn't really related to Dapper; the exact same problems would occur for any similar usage - whether ADO.NET, Dapper, EF, or anything else)

Additional speculation (comes "after" the below historically, but "before" in terms.of things to try) based on my thoughts in a comment: without changing the property at all, you could try adding

Azure SQL is known for having "transient errors" occasionally when connecting or issuing commands. Of course there could be other causes also for your specific error (network devices issues, hardware issues), but since they only happen occasionally and are not reproducible, the transient error handling solutions still apply.

In Azure, there can be a number of causes for these transient issues, often related to some auto-scaling or an infrastructure issue that is being mitigated behind the scenes by Azure engineers or by some Azure auto-healing, for which you will normally not have any visibility.

The main solution and the one recommended strongly by Microsoft is to implement retry handling to handle these "transient" issues. You could use a .NET library like Polly (https://github.com/App-vNext/Polly), or build your own with a while loop (https://docs.microsoft.com/en-us/sql/connect/ado-net/step-4-connect-resiliently-sql-ado-net?view=sql-server-ver15#step-2b-copy-and-paste-sample-code). They often recommend a retry back-off strategy that includes retrying quickly for the first retry, and if it keeps failing, then increase your retry intervals on subsequent retries.

Make sure you log the exceptions when retrying, so that you can determine if the issue becomes more persistent.

More info about Azure SQL transient errors: https://docs.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-connectivity-issues

And transient error handling: https://docs.microsoft.com/en-us/azure/architecture/best-practices/transient-faults

You are missing a return statement in the Handle method, but adding it alone won't fix the compilation you need to translate Admin returned by _userService.Login to BaseResponse. Also since _userService.Login is a sync method - no need for Task.Run and assync-await - use Task.FromResult instead. Something like this (assiming the existence of corresponding BaseResponse ctor):

@jwdonahue put me on the right track...

In my OrderDto class I needed a constructor where I initialized my fields:

I was able to reproduce this issue in a test. The test below shows that OP's original code works when using @tableName instead of $tableName inside SQL.

The problem is in your function GetList when you call xml2js parser. You are passing the callback to the parse function, and returning a value from a callback. Returning value from callback is not the same as returning a value from the outer function call. The solution is to wrap the function call into a promise and return the promise.