POSTGRESQL CASE STATEMENT HOW TO
POSTGRESQL CASE STATEMENT PLUS
POSTGRESQL CASE STATEMENT FREE

Use those practices that best benefit your needs and goals. Your particular goals and needs may vary. The majority, if not all, of the examples provided, is performed on a personal development/learning workstation-environment and should not be considered production quality or ready. They are not the utmost best solution(s).

POSTGRESQL CASE STATEMENT HOW TO

Among those, he shares a love of tabletop RPG games, reading fantasy novels, and spending time with his wife and two daughters.ĭisclaimer: The examples presented in this post are hypothetical ideas of how to achieve similar types of results. Other favorite activities find him with his nose buried in a good book, article, or the Linux command line. Josh Otwell has a passion to study and grow as a SQL Developer and blogger.

POSTGRESQL CASE STATEMENT FREE

To receive email notifications (Never Spam) from this blog (“Digital Owl’s Prose”) for the latest blog posts as they are published, please subscribe (of your own volition) by clicking the ‘Click To Subscribe!’ button in the sidebar on the homepage! (Feel free at any time to review the Digital Owl’s Prose Privacy Policy Page for any questions you may have about: email updates, opt-in, opt-out, contact forms, etc…)īe sure and visit the “Best Of” page for a collection of my best blog posts. Have I mentioned how much I love a cup of coffee?!?! Visit the Portfolio-Projects page to see blog post/technical writing I have completed for clients. Please share your findings here, with someone else you know who would get the same value out of it as well.

I truly hope you discovered something interesting and enlightening. Thank you for taking the time to read this post. Like what you have read? See anything incorrect? Please comment below and thanks for reading!!!Įxplore the official PostgreSQL 11 On-line Documentation for more information. However, I hope that by reading this post, you have a general understanding of this form of CASE and can find a use case for it in your day-to-day workflow. The complexity of just what can be accomplished with the searched CASE expression obviously goes way further than that of the simple example covered here. The ELSE clause portion could be thought of as the ‘default’ and covers any other row that does not meet the boolean conditional check of the other WHEN/ THEN clauses. The same applies to other rows in the result set according to those SUM ( ) values and conditional checks. For instance, since the 3rd row SUM ( ) value of 167.67 meets the WHEN/ THEN conditional of BETWEEN 160 AND 170, that row has a ‘member_status’ of bronze. In the above query results, for each row, due to the WHEN/ THEN clauses, a ‘member_status’ column is displayed (with a designated ‘label’) according to the SUM ( ) spending amount. WHEN SUM (p.amount ) BETWEEN 160 AND 170 THEN 'bronze'įirst_name | last_name | sum | member_status WHEN SUM (p.amount ) BETWEEN 170 AND 190 THEN 'gold' WHEN SUM (p.amount ) > 190 THEN 'platinum' SELECT c.first_name, c.last_name, SUM (p.amount ), To return the desired results we listed out above, CASE is our friend. Let’s visit the below query for a breakdown of where they will be ‘classified’ according to the total amount spent.

Finally, the ‘standard’ members are those who have met the greater than 150 criteria, yet have not quite eclipsed the 160 spending mark.

Spending totals ranging from 160 to 170 are ‘bronze’ members.

Amounts more than 170 but less than 190 are ‘gold’ members.

POSTGRESQL CASE STATEMENT PLUS

Totals spent of 190 plus are ‘platinum’ members.

Maybe we are sending them a discount for an upcoming sale. Perhaps for reporting purposes, we want to distinguish these customers with a level of some sort, according to their spendings. SELECT c.first_name, c.last_name, sum (p.amount )

Postgresql case statement