Timeline for Left Joining Tables with tables that have subquery aggregate
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2016 at 20:14 | comment | added | Zaphodb2002 | Whoops used the entire APPLY alias rather than creating an internal alias for POSEligibility. Andy Jones' answer is slightly better though, because mine doesn't account for multiple eligibilities correctly. The OUTER APPLY is useful when you need to do something (like check a max value) against each row. | |
| Oct 31, 2016 at 20:05 | history | edited | Zaphodb2002 | CC BY-SA 3.0 |
screwed up the aliases
|
| Oct 31, 2016 at 19:52 | comment | added | Joshua Barrett | Line 13 pos.personID cannot be bound. I'm not familiar with the OUTER APPLY. I added on line 12 FROM dbo.POSEligibility AS pos. And now it's saying per.personID not found. | |
| Oct 31, 2016 at 19:31 | history | edited | Zaphodb2002 | CC BY-SA 3.0 |
words
|
| Oct 31, 2016 at 19:25 | history | answered | Zaphodb2002 | CC BY-SA 3.0 |