rosie | building JavaScript objects | Development Tools library

You should use the json module to load in JSON data as opposed to reading in the file line-by-line. Whatever procedure you build yourself is likely to be fragile and less efficient.

Here is the looping structure that you're looking for:

You importing import * as firebase from 'firebase' in the top of your file..Try to import this line and tell me if it works. import firebase from "firebase/compat/app";

Some paths of the firebase have changed a long time ago so if you are watching legacy code snipets maybe you will have errors.

While Caleb's answer did not really help in my case, I think it was a bit of a pointer as to what was going wrong. I did not intend to write a svelte-focused Component library, but rather a general model/factory library to be reused between the front- and backend.

I did a couple of things since this issue occurred and here is a list of things I think went wrong:

• Local linking of the npm package into my project caused issues (npm link). I have very little experience with all the build tools in sveltekit but figured out where those stale/non-functional libs are referenced from. I deleted the node-modules/.vite folder which sometimes resolved my issues (I greped for seemingly cached values which led me to this directory. In my dev experience quite uncommon to have found build artifacts in node-modules, so that was a bit tedious to find in that place).
• I converted my npm package to a hybrid ESM/CJS module (previously CommonJS only). I'm unsure whether that resolved the initial issues, but might be worth a try.

I think the main issue was the local linking and some sort of build caching going on in vite.

That being said, I haven't encountered any issues with the library ever since.

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

You're importing Firebase v9 (as far as I can tell) with:

String literals in C++ have types of constant character arrays that used as expressions with rare exceptions are converted to pointers to their first characters of the type const char *. But the first parameter of your constructor has the type char * instead of const char *. So the compiler issues an error.

Also the constructor can produce a memory leak due to the default argument where a memory is dynamically allocated but not deleted.

You could declare the constructor at least the following way

I need to write the SQL query to return the number of employees for each department. However, my below command is not correct:

This is not what you ask for.

You get the join correct, but you ask for:

SELECT COUNT(Employees.employment_id)

The count how often different employment id's exist - which is 1 for an employee in one department, or X with X being the number of entries in the join. As the department_id entry is part of the employee table, this CAN NOT HAPPEN. TOTALLY not asking what you want.

I'm using the LEFT JOIN here because I am returning the result from the Employees table is this right?

Depends - a normal join should work here. Left is only sensible if the other side can be empty - which I would assume is not possible (there are no rows with Employees.department_id being NULL).

You you want is a count (without anything in the brackets) and a group by department_id. And obviously the department id:

SELECT Department.department_id, count() FROM....

Furthermore, are there any tips to speed up SQL Server's performance?

Just pointing you to https://use-the-index-luke.com/ - indices are a cornerstone for any decent performance.

Ignoring your second question - one per question please.

Here is how to map the "Account indicator" using groupby/transform+nunique.

Please update your output with an example for the other part of the question on the balance:

try changing this block: