The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Initial results were discovered to be due to either undue Russian influence on the voting, Fake News, or an inability to count without using my fingers.
Since we have a tie, with one expressed preference for a second vote from super, we'll move to "limited themes" with a "themed week" starting on the first Monday of each month for simplicity.
So next week is unthemed, the following week will be themed.
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
Fine by me, and we can always re-review in 2-3 months to see if people are happy.
I would suggest though that during themed weeks the post it marked as such, and it also includes what the actual theme of the week is, so as to save people from having to look up past solutions to work out what the theme is supposed to be.
Well we could do a best of both worlds scenario. To satisfy the 3 voters, lets do themes on the first week of each month. Then to satisfy the 4 voters, we will completely get rid of themes for the rest of the month...
In Database 1 the code read a list of Transaction, as source data
In Database 2, the code will INSERT Transaction, and UPSERT (i.e. maybe insert, maybe update) linked Box, Order and Plate records (i.e. normalise data on the fly)
I.e. it should convert source line data into a tree structure in target database
I am not using EntityFramework autodetect, I detect meself.... (maybe I could have, just don't like it...) and also I am using EntityFramework Bulk Operation extension (maybe not needed since I am limited to 2000 record at a time due to a select with Contains(), doesn't support autodetect change btw)
At any rate the tree update code was becoming increasingly ever so painfully convoluted as the business people thought it would be cool to include this and that info....
And then ... breakthrough happened!
The tree bulk UPSERT (i.e. UPDATE+INSERT) code became simple again!