amount is a number, but the expressions in the case clauses only evaluate to booleans; the values will never match. You could always do switch (true) { case (amount >= 7500 && amount < 10000): // Code break; case (amount >= 10000 && amount < 15000): // Code break; // etc. } It works because … Read more
Bash case does not use regular expressions, but shell pattern matching only. Therefore, instead of regex ws-[0-9]+\.host\.com you should use pattern ws*.host.com (or ws-+([0-9]).host.com, but that looks a bit advanced and I’ve never tried that 🙂
SELECT UPPER(firstname) FROM Person SELECT LOWER(firstname) FROM Person
Your query would work already – except that you are running into naming conflicts or just confusing the output column (the CASE expression) with source column result, which has different content. … GROUP BY model.name, attempt.type, attempt.result … You need to GROUP BY your CASE expression instead of your source column: … GROUP BY model.name, … Read more
CASE is more like a switch statement. It has two syntaxes you can use. The first lets you use any compare statements you want: CASE WHEN user_role=”Manager” then 4 WHEN user_name=”Tom” then 27 WHEN columnA <> columnB then 99 ELSE -1 –unknown END The second style is for when you are only examining one value, … Read more
Yes, something like this: SELECT id, action_heading, CASE WHEN action_type=”Income” THEN action_amount ELSE NULL END AS income_amt, CASE WHEN action_type=”Expense” THEN action_amount ELSE NULL END AS expense_amt FROM tbl_transaction; As other answers have pointed out, MySQL also has the IF() function to do this using less verbose syntax. I generally try to avoid this because … Read more
Assigning a value to a local variable and then returning that at the end is considered a good practice. Methods having multiple exits are harder to debug and can be difficult to read. That said, thats the only plus point left to this paradigm. It was originated when only low-level procedural languages were around. And … Read more
I think what you are asking for will work by joining the Initial table to both Option_A and Option_B using LEFT JOIN, which will produce something like this: Initial LEFT JOIN Option_A LEFT JOIN NULL OR Initial LEFT JOIN NULL LEFT JOIN Option_B Example code: SELECT i.*, COALESCE(a.id, b.id) as Option_Id, COALESCE(a.name, b.name) as Option_Name … Read more
Remove the course_enrollment_settings.base_price immediately after CASE: SELECT CASE WHEN course_enrollment_settings.base_price = 0 THEN 1 … END CASE has two different forms, as detailed in the manual. Here, you want the second form since you’re using search conditions.
Try this query – SELECT t2.company_name, t2.expose_new, t2.expose_used, t1.title, t1.seller, t1.status, CASE status WHEN ‘New’ THEN t2.expose_new WHEN ‘Used’ THEN t2.expose_used ELSE NULL END as ‘expose’ FROM `products` t1 JOIN manufacturers t2 ON t2.id = t1.seller WHERE t1.seller = 4238