Just like every year, a mararhon around Lubin was in last days of August 2019. Some people ran 100 km or less, other used bicycles and also many different distances. It was my third start on this marathon, and like every year, I decided to ride 110 km, the longest one. Weather was great – especially in the morning. All day was sunny, without rain, but also hot, there was about 32 degree Celsius (~92 degree Fahrenheit).
It wasn’t race, but great marathon: you could choose start time (from 6am to 10am, every 30 minutes) and also choose path, but must visit all eleven control points. As every year, I rode some in forrest, some on roads, and also lost way few times. Theoretically the best option is to ride across the red trail, but some sections are terrible for gravel or cx bikes. Overall, it was fantastic day!
I visited Jizera Mountains again in this year. It was great time with a lot of hard cycling – not 100 km, but more that 2000 m uphill. Ufff, it was difficult, but amazing. I made a lot of personal records in many segments on Strava. Yep, it wasn’t most important, but it always something good. When next time? Maybe this year? Not sure, but want visit Jizera again! One info: tubeless saves me this time, but I disovered this after went back to home. I will wrote about that in one of next posts.
One of the most common problems with databases are sorting. Let’s see an simple example: we use MySQL/MariaDB and have table with some data. We want to sort this data. Everything is ok if we use only values in the same type in field, for example numeric (maybe some amount?), strings (titles), dates, keys etc. But what if field is custom, user-typed data and may contain many types? In that case, we have big problem, because standard sorting is not enought, it will not work. Example, value: “11”, “1”, “2”, “3”, “2a” will be sorted in order: 1, 11, 2, 2a, 3, not as we expected i.e. 1, 2, 2a, 3, 11. The solution is to use natural sorting.Continue reading “MongoDB – Natural sort”