• 0 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle















  • Moops@lemmy.worldtoProgrammer Humor@programming.devIt's that time of the year again!
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    1
    ·
    edit-2
    7 months ago

    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)