Gordon | Gordon is an Android instrumentation test runner | Unit Testing library

If you didn't have any condition on employee ID at all you'd end up with records where a self-match had occurred, e.g. the results would show "Gracie Gardner was hired on the same day as Gracie Gardner"

We could then put ON e1.employee_id <> e2.employee_id - this would prevent Gracie matching with Gracie, but you'd then find "Gracie Gardner was hired on the same day as Summer Payne" and "Summer Payne was hired on the same day as Gracie Gardner" - i.e. you'd get "duplicate records" in terms of "person paired with person", each name being mentioned both ways round

Using greater than prevents this, and effectively means that any given pair of names only appears once. Because Gracie's ID is less than Summer's, you'll get Gracie in e1 paired with Summer in e2 but you won't get Summer in e1 paired with Gracie in e2

Another way of visualizing it is with a square/matrix

The issue is with lazy val app = (project in file("app")). Assuming a single module project with no module named app, sbt-assembly will create a directory named app and attempt to stuff the build in there. However, since the main class is not in the app bundle, the class will not be added to the jar file.

The correct way to do this is:

lazy val app = (project in file(".")), which specifies the current directory as the one to look for the main class. So this was not really an issue with knowing how to use the sbt-assembly plugin, but a more general issue with specifying projects in an sbt build.

It's counterintuitive, but you need to set the margins to allow space for the tick labels and Y axis label.

dc.js does not automatically lay out elements that rely on text size, because it is complicated and expensive to do so.

Instead it requires the user to set margins that leave room. The margins are used to shrink and offset the chart area.

The default margins are {top: 10, right: 50, bottom: 30, left: 30}; these settings are just a guess. You might try

Unfortunately you are neither using bibtex nor biblatex, so one needs a bit of a hack to add numbers to the bibliography.

You could include the following file in your header:

try this:

I believe the cause is the GROUP BY is calculated before the PARTITION BY and breaks when the GROUP BY drops cuisine as it attempts to aggregate.

This is exactly what happened.

Related: A Beginner’s Guide to the True Order of SQL Operations

Alternative approach:

I was wrong that I misunderstood that you're focus on Final_Group. If not, please let me know My approach is based on distance between samples.

OK, so I finally found out what was the problem. For some reason, I'm not able to CAST to float inside the MAX. If I remove both CAST from the query, the exception is gone and everything works. I'm not sure why this happens, and if anyone could explain that, it would be very helpful as I need to cast those values to float. Also, if I SELECT more columns, it is necessary to add said columns into the GROUP BY statement. Anyways, here's the modified code that works:

EDIT: Found out the way to cast them. It turns out I was getting some nulls, some blank fields, and I was trying to assign a number to a string. This is the code now:

As is mentioned in this question Why is the Python CSV reader ignoring double-quoted fields? you'll need to add the skipinitalspace param so that csv.reader will understand the quotes.