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 🙂
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
This won’t directly solve your problem as you want to switch on your own user-defined types, but for the benefit of others who only want to switch on built-in types, you can use the TypeCode enumeration: switch (Type.GetTypeCode(node.GetType())) { case TypeCode.Decimal: // Handle Decimal break; case TypeCode.Int32: // Handle Int32 break; … }
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
That format requires you to use either: CASE ebv.db_no WHEN 22978 THEN ‘WECS 9500’ WHEN 23218 THEN ‘WECS 9500’ WHEN 23219 THEN ‘WECS 9500’ ELSE ‘WECS 9520’ END as wecs_system Otherwise, use: CASE WHEN ebv.db_no IN (22978, 23218, 23219) THEN ‘WECS 9500’ ELSE ‘WECS 9520’ END as wecs_system
declare @locationType varchar(50); declare @locationID int; SELECT column1, column2 FROM viewWhatever WHERE @locationID = CASE @locationType WHEN ‘location’ THEN account_location WHEN ‘area’ THEN xxx_location_area WHEN ‘division’ THEN xxx_location_division END
First off, the CASE statement must be part of the expression, not the expression itself. In other words, you can have: WHERE co.DTEntered = CASE WHEN LEN(‘blah’) = 0 THEN co.DTEntered ELSE ‘2011-01-01′ END But it won’t work the way you have written them eg: WHERE CASE LEN(‘TestPerson’) WHEN 0 THEN co.personentered = co.personentered ELSE … Read more
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
Sometimes it is helpful to have multiple cases associated with the same code block, such as case ‘A’: case ‘B’: case ‘C’: doSomething(); break; case ‘D’: case ‘E’: doSomethingElse(); break; etc. Just an example. In my experience, usually it is bad style to “fall through” and have multiple blocks of code execute for one case, … Read more
case_when(), which was added to dplyr in May 2016, solves this problem in a manner similar to memisc::cases(). As of dplyr 0.7.0, for example: mtcars %>% mutate(category = case_when( cyl == 4 & disp < median(disp) ~ “4 cylinders, small displacement”, cyl == 8 & disp > median(disp) ~ “8 cylinders, large displacement”, TRUE ~ … Read more