; found this in the back for you should still work though

At the very least I'd try to clean up that fuzzy condition on behavior to anticipate any bad or inconsistent data entry.

WHERE UPPER(TRIM(behavior)) = 'NICE'

Depending on the possible values in behavior, adding a wildcard or two might be useful but would need to know more about that field to be certain. Personally I'd rather see if there was a methodology using code values or existing indicators instead of a string, but that's often just wishful thinking.

Edit: Also, why dafuq we doing a select all? What is this, intro to compsci? List out the values you need, ya heathen ;)

(This is my favorite Xmas meme lol)

Need to normalize the database. I would add a join to a BehaviorTypes table.

Edit: or, if the only options are naughty or nice, make it a boolean.

You need semicolons if it is a script with multiple commands to separate them. It is not needed for a single statement, like you would use in most language libraries.

Honest question, which ones wouldn't it work with? Most add a semicolon to the end automatically or have libraries and interfaces saved me a million times?

it also implies that naughty or nice is an either or thing and not a weighted thing from an incidents table. the good place lied to us.

Uuugghhh noooo! Ess Kyoo Ell!! ESS KYOO ELL!!! brandishes flaming pitchfork!

Squirrel works too though.

"Squill"

Sequel to what?

He drops when you are sleeping. He drops when you’re awake.

Pencil

Gameboy Pocket. Gameboy Camera. Gameboy Printer.

Both the perfect balance of “nostalgia” and “ridiculous”.

Cut to Mrs Claus baking a spice cake:

She's all alone, all alone, in her time of spice

He knows you're not in the sudoers file

So he'll report your ass again