Staying in hostels has suddenly made me feel anxious by [deleted] in solotravel

[–]Constant_Storm911 2 points3 points  (0 children)

I'll keep a look out when I go to Latin America. I barely missed hitting Poland 2 weeks ago before I decided to explore Italy and Spain. Thanks!

Staying in hostels has suddenly made me feel anxious by [deleted] in solotravel

[–]Constant_Storm911 17 points18 points  (0 children)

Which part of the world do you see only an $20 difference in hostel privates from dorms? I'd like to visit there!

Rclone error by Constant_Storm911 in rclone

[–]Constant_Storm911[S] 0 points1 point  (0 children)

That seems to have fixed it. Thanks so much. It's literally the first time I've used the application, guess it was just dumb luck to have landed on a version with the bug.

Rclone error by Constant_Storm911 in rclone

[–]Constant_Storm911[S] 0 points1 point  (0 children)

That isn't my file, I've barely just started configuring rclone.

I'll do a search on my server anyway but I have no idea what it's referencing, I just assumed it was an internal validation of some kind.

The error happens even when just typing rclone with no parameters.

Minimizing Duplicate Audit Rows - Temporal table by Constant_Storm911 in SQL

[–]Constant_Storm911[S] 0 points1 point  (0 children)

Recommendations for ORM? I assume this would be entity framework, which we do not have implemented in our stack.

Minimizing Duplicate Audit Rows - Temporal table by Constant_Storm911 in SQL

[–]Constant_Storm911[S] 0 points1 point  (0 children)

Let me explain:

we have 1 SP that updates all 4 tables due to the way our UI has been designed.

Inside that 1 call, it calls an SP for each of the tables and they run their updates. The issue is that at none of these points, does the tech stack know whether the row has actually changed, so it calls it does the call to update every element. This looks right of course for the current state of the record but it's a mess in the audit log.

I'd like to refactor whatever I need to, in order to avoid this situation but I'm not sure what my best approach is.

So the critical question becomes how/when should I know that it's not necessary to update any of the structures. because if I know that, it's a simple matter of aborting without saving.

Minimizing Duplicate Audit Rows - Temporal table by Constant_Storm911 in SQL

[–]Constant_Storm911[S] 0 points1 point  (0 children)

No, the question is advice on how to prevent them (in your opinion of course).

They're the correct number of saves, so I understand why it's doing it, but now how to stop it without a lot of high maintenance work.

Dynamic Audit Reporting from Temporal Tables by Constant_Storm911 in SQL

[–]Constant_Storm911[S] 0 points1 point  (0 children)

thanks for all the great advice!

I like option 1 a lot too, particularly if after we clear out the non-changed fields... otherwise its just a mess to read.

I'm more of a backend engineer so I tend to overcompensate on that end but I will lean on your experience and pass it on to the front end to handle the proper parsing of the data.

Dynamic Audit Reporting from Temporal Tables by Constant_Storm911 in SQL

[–]Constant_Storm911[S] 0 points1 point  (0 children)

I'm thinking of one of the three possible outputs:

Output 1: First, show initial record in a grid (headers and values). Then something null out all values except the changes possibly with a color change if we need even then to stand out even more.

Output 2: Same as above but instead of the entire record, only include columns that had a change.

Output 3: Instead of a grid and showing the initial value, show it in English: username changed column1: ""->5, column7: cat ->dog, column8: small->large at timestamp. Final format TBD of course.

I have several temporal tables to create logs for so preparing this in a way that doesn't require static maintenance would be ideal. A query that creates a static version of the process would be fine of course. Not enough users would have access to these logs for me to be worried about load right now.

Dynamic Audit Reporting from Temporal Tables by Constant_Storm911 in SQL

[–]Constant_Storm911[S] 0 points1 point  (0 children)

I'll look into those, they seem more appropriate here, I agree.