Don't worry. Not everyone knows it...

In my previous post, I discussed about getting the result set which lies between the given date range. This time, let’s take an another interesting example, wherein we need to transform the number to rows into number of columns as our result set. Consider below data for which we need to write query: let demoData = datatable(Environment: string, Feature:string, Location:string, Version: string)     [          "dev" ,  "Feature1" ,  "Site1" ,  "v1" ,          "test" ,  "Feature1" ,  "Site2" ,  "v2" ,          "prod" ,  "Feature1" ,  "Site3" ,  "v3" ,         "dev" ,  "Feature2" ,  "Site1" ,  "v4" ,          "test" ,  "Feature2" ,  "Site4" ,  "v5" ,          "dev" ,  "Feature3" ,  "Site1" ,  "v6" ,          "test" ,  "Feature3" , 

I n continuation to my previous post on ' Get Min/Max from each category ', this time let’s do one of the most demanded queries with filter criteria on date time field. For the purpose of simplicity and keep this article more focused, I have removed data from all the additional columns as shown below: GenerationDate DescriptionTitle DescriptionDetail FeedKey 2020-10-02 00:00:00:0000000 … … … 2020-10-21 00:00:00:0000000 … … … 2020-10-21 00:00:00:0000000 … … … 2020-10-21 00:00:00:0000000 … … … 2020-10-21 00:00:00:0000000 … … … 2020-10-22 00:00:00:0000000 … … … 2020-10-22 00:00:00:0000000 … … … Query description The idea is to fetch all the records, which occurred in past 20 days of GenerationDate . Approaches Now to achieve our expected result, there could be more than a way.   One way could be: Approach 1 Find out the date which fall exactly twenty days back using ago(…) and then use conditional operator (<= and >=) to achieve this result.  Above approach would

In the field of software development, code review plays a very vital role. It not only enhances the code quality, but also identifies issues before the code goes into the tester’s hand. T hroughout my development experience, I came across many amazing guidelines that can contribute to an effective code review. So, as part of this article I’m going to list down all those points. Naming Conventions, Data types, Sizes and Comments V ariable names should be small but self-explanatory. Based on the language and platform, standards and casing should be followed. Always prefer field names using adjective or noun. Prefer to use PascalCasing for resource keys. Always prefer to name events with a verb. It’s good to think about tense while naming events, i.e. rendered, rendering, etc. Keep method size as small as possible. I personally prefer, size of method body of <=12 lines. So, that complete method can be seen without scrolling the screen. All the parameters should pass validation check be

In continuation to my previous post on 'Get Categorial Count' , this time let’s get our hands dirty with one more query related to filter criteria for date time field. Below is the sample data on which we are going to query: GenerationDate IngestionTime DescriptionTitle DescriptionDetail FeedKey 2020-05-21 00:00:00:0000000 2020-05-25 02:00:00:0000000 Schedule Task Read feed from server 1 acbf-uhef-4t5i-dfff 2020-05-21 00:00:00:0000000 2020-05-25 03:00:00:3000000 Schedule Task Read feed from server 1 acbf-uhef-4t5i-dfff 2020-05-21 00:00:00:0000000 2020-05-25 03:00:00:3500000 Schedule Task Read feed from server 1 acbf-uhef-4t5i-dfff 2020-05-21 00:00:00:0000000 2020-05-25 03:00:00:3000000 Monitoring Task Monitoring failed for LOC lcbf-u78f-4