Subsequent queries

[John Currey]

Hi, 

I'm starting to get back to writing queries and I noticed subsequent queries do not appear to be working. For example:

NHL

• date,R(team),R(o:team)@season=2021 and H | $2,$3@today in date

https://s3.sportsdatabase.com/NHL/query.html?sdql=date%2CR%28team%29%2CR%28o%3Ateam%29%40season%3D2021+and+H+%7C+%242%2C%243%40today+in+date&submit=++S+D+Q+L+%21++

MLB

• date,R(team),R(o:team)@season=2022 and H | $2,$3@20220522 in date

https://s3.sportsdatabase.com/MLB/query.html?sdql=date%2CR%28team%29%2CR%28o%3Ateam%29%40season%3D2022+and+H+%7C+%242%2C%243%4020220522+in+date&submit=++S+D+Q+L+%21++

NBA

• date,R(team),R(o:team),A(points)@season=2021 and H | $2,$3,$4@$4>100
  

https://s3.sportsdatabase.com/NBA/query.html?sdql=date%2CR%28team%29%2CR%28o%3Ateam%29%2CA%28points%29%40season%3D2021+and+H+%7C+%242%2C%243%2C%244%40%244%3E100&submit=++S+D+Q+L+%21++

This does work in the NFL:

• R(date),R(team),A(rushing yards)@team and season | $2,$3@$3>150

https://s3.sportsdatabase.com/NFL/query.html?sdql=R%28date%29%2CR%28team%29%2CA%28rushing+yards%29%40team+and+season+%7C+%242%2C%243%40%243%3E150&submit=++S+D+Q+L+%21++

Thanks.

[Joe Meyer]

John and SDQLAPI Friends,

I see that the first 2 are  'irregular' queries: they have a combination of aggregator and non-aggregator fields.

The 3rd one works because the fields are all aggregators.

Best regards,

Joe Meyer

Sports Database LLC

--

---
You received this message because you are subscribed to the Google Groups "SDQL API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sdqlapi+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sdqlapi/28c2b992-c408-4e0f-8d01-9be1bc142c1bn%40googlegroups.com.

[John Currey]

Got it, thanks!

[John Currey]

I thought I understood, but I do not. I'm sure those queries worked as is in S2. 

Here is the example from the Subsequent Queries page of the manual - https://s3.sportsdatabase.com/static/Manual/subsequent.html.

• date,R(team),A(W) @ tA(points) > 10+oA(points) and team | $2,$3 @ 20170112 in $1

Not all parameters in that example are aggregators. The query fails:

https://s3.sportsdatabase.com/NBA/query.html?sdql=date%2CR%28team%29%2CA%28W%29+%40+tA%28points%29+%3E+10%2BoA%28points%29+and+team+%7C+%242%2C%243+%40+20170112+in+%241&submit=++S+D+Q+L+%21++

Thanks

[Joe Meyer]

John and SDQLAPI Friend,

I see that, indeed, SDQL3 is not handling irregular queries properly.

Thanks for the good debugging and I'll get my best Python programmer on that.

Best regards,

Joe Meyer

Sports Database LLC

To view this discussion on the web visit https://groups.google.com/d/msgid/sdqlapi/a5c7152b-1715-48d1-bac4-3ff7a661649bn%40googlegroups.com.

[Joe Meyer]

John and SDQL API Friends,

I believe subsequent queries are now working correctly.

Please let me know if you continue to see errors.

Best regards,

Joe Meyer

Sports Database LLC

To view this discussion on the web visit https://groups.google.com/d/msgid/sdqlapi/a5c7152b-1715-48d1-bac4-3ff7a661649bn%40googlegroups.com.

[John Currey]

Thanks Joe!

[John Currey]

I'm trying a simple subsequent query. I believe it should show home teams and their opponent who are playing on 6/26. It's only showing the Twin and White Sox who are not playing each other today and the Twins are away. 

https://s3.sportsdatabase.com/MLB/query.html?sdql=date%2CR%28team%29%2CR%28o%3Ateam%29%2CR%28site%29%40season%3D2022+and+H+%7C+%242%2C%243%2C%244%4020220626+in+date&submit=++S+D+Q+L+%21++

If I eliminate future games, it's better, but only shows the Astos/Yankees game.

https://s3.sportsdatabase.com/MLB/query.html?sdql=date%2CR%28team%29%2CR%28o%3Ateam%29%2CR%28site%29%40season%3D2022+and+H+and+date%3C%3Dtoday+%7C+%242%2C%243%2C%244%4020220626+in+date&submit=++S+D+Q+L+%21++

Thanks. 

[Joe Meyer]

John and SDQL Friends,

The Replace aggregator provides the last value of its argument for each query group.

The R(team) in your primary SDQL:

date,R(team),R(o:team),R(site)@season=2022 and H  

simply provides the last value of team for season=2022 and H - which happens to be the White Sox

To build a subsequent query, I'd suggest first looking at the results of the primary query.

best regards,

Joe Meyer

Sports Database LLC

To view this discussion on the web visit https://groups.google.com/d/msgid/sdqlapi/892747c5-3528-4038-9db0-700e9928fd4dn%40googlegroups.com.

[John Currey]

That makes sense. I thought of that but was confused when this didn't return anything. 

https://s3.sportsdatabase.com/MLB/query.html?sdql=date%2Cteam%2Co%3Ateam%2Csite%40season%3D2022+and+H++%7C+%242%2C%243%2C%244%4020220626+in+date&submit=++S+D+Q+L+%21++

[Joe Meyer]

John and SDQL Friends,

I think you want to start with finding the dates of all team-opp matchup, like this:

date,R(team),R(o:team)@season=2022 and H and team and o:team|

Best regards,

Joe Meyer

Sports Database LLC

To view this discussion on the web visit https://groups.google.com/d/msgid/sdqlapi/8658f127-ebf9-472d-9247-395286b100c5n%40googlegroups.com.

[John Currey]

OK, got it.  Thanks. 

[John Currey]

I notice that the alias works as expected in the subsequent query as a field, but the alias defined in the main query does not become the column heading when the $variable is used as it did in S2. 

https://s3.sportsdatabase.com/MLB/query.html?sdql=date%2CR%28team%29+as+%27Team%27%2CR%28o%3Ateam%29+as+%27o%3Ateam%27%40season%3D2022+and+H+and+team+and+o%3Ateam%7C+Team%2C%243%40today+in+date&submit=++S+D+Q+L+%21++