Either your query has no matching results or we're having trouble interpreting your SDQL.
You are welcome to post it at the Discord group with a thorough, concise explanation of what you are trying to do.
Query Fundamentals
For more detailed information on SDQL including manuals and videos go HERE
The syntax for access to the NBA team data is: game
reference:parameter. To see the date, team, and opponent where the team scored
+120 points after scoring +120 runs in the previous game use the SDQL:
date,team,o:team@points>120 and p:points>120
The syntax for access to
the NBA player data:
[team:]player name:game reference:parameter. To see the date, team, opponent and
number of points by Kobe Bryant in the game after he scored more than 30 use the
SDQL: date,team,o:team,Kobe Bryant:points@Kobe Bryant:p:points>30
Query Fundamentals:
A query consists of one or more clauses joined by and or or.
Examples:
The query:
50 < Kobe Bryant : points
and
site = away
The explain:
returns home games where Kobe Bryant scored more than 50 points on the road
If no player is given then results for the team are checked. E.g.
The query:
120 < Bulls : points
and
site = home
returns games in which the Bulls scored more than 120 points at home
points < 60
returns games when the team scored fewer than 60 points
Multiple conditions can be imposed using a comma delimited format.
points < 90,100,110
gives results grouped by points < 90, points < 100, and points < 110
You can comma-group on both sides of the inequality as per:
70,80,90,100 < points < 90,100,110
Game Reference
p :
team's previous game
N :
next match up
on :
opponent's next game
P :
previous match up
S :
starter's previous match up start
n :
team's next game
s :
starter's previous start
op :
opponent's previous game
Examples:
The query:
100 < t:rushing yards
and
to:rushing yards < 100
The explain:
Use this SDQL to see how teams do when rushing for more than 100 yards while holding their opponent to few than 100 yards
Queryable Fields
attendance, biggest lead, coach, conference, date, day, division, faceoffs won, game number, giveaways, goals, hits, lead changes, line, linesmen, losses, margin, matchup losses, matchup wins, month, opponent, opponents, ou margin, ou streak, over, overtime, penalties, penalty minutes, period scores, pl margin, playoffs, power play goals, power plays, puck line, puck line goals, referees, regulation line, rest, rot, season, shots on goal, site, site streak, srslg, start time, streak, takeaways, team, times tied, total, under, wins
The query:
40 < p:points
and
40 < p2:points
and
40 < p3:points
and
40 < p4:points
Use this SDQL to see how teams do after scoring more than 40 points their last four games
2*P:points in the paint < Po:points in the paint
and
P:season = season
return games in which the team was outscored in the paint by a factor of 2 in their previous match up
The query:
0.25*p:points<=p:fast break points
and
po:points
The explain:
return games with a team off a win in which they scored at least 25% of their points from fast breaks
Short Cuts
H, A, W, L, F, D, O, U, C, X are short cuts for
home,away,win,loss,favorite,dog,over the total,under the total, and conference.
As with the parameter prefixes, these can be strung together without limit.
Examples:
The query:
HF
×
and
p:HFL
×
and
pp:HFL
×
The explain:
returns home favorites after they just lost as home
favorites their last two games
P:O
×
and
PP:O
×
and
PPP:O
×
and
PPPP:O
×
and
PPPPP:O
×
and
PPPPPP:O
×
The explain:
returns games where teams have gone over the total their
last six matchups
In addition to the above single letter short cuts the
following abbreviations are available:
NHL Trend Builder
For a more detailed review of how to use the Trend Builder, go HERE
NHL Field Options
as
attendance+
biggest lead+
coach+
conference+
date
day+
division+
faceoffs won+
game number+
giveaways+
goals+
hits+
lead changes+
line+
linesmen+
losses+
margin+
matchup losses+
matchup wins+
month+
opponent+
opponents+
ou margin+
ou streak+
over+
over_invest+
over_profit+
overtime+
penalties+
penalty minutes+
period scores+
pl margin+
pl_invest+
pl_profit+
playoffs+
power play goals+
power plays+
puck line+
puck line goals+
referees+
regulation line+
rest+
rot+
season+
shots on goal+
site+
site streak+
srslg+
start time+
streak+
su_invest+
su_profit+
takeaways+
team
times tied+
total+
under+
under_invest+
under_profit+
wins+
Day+
Opp+
Final+
Rest+
SUr+
OUr+
ot+
Queryable Fields
attendance, biggest lead, coach, conference, date, day, division, faceoffs won, game number, giveaways, goals, hits, lead changes, line, linesmen, losses, margin, matchup losses, matchup wins, month, opponent, opponents, ou margin, ou streak, over, overtime, penalties, penalty minutes, period scores, pl margin, playoffs, power play goals, power plays, puck line, puck line goals, referees, regulation line, rest, rot, season, shots on goal, site, site streak, srslg, start time, streak, takeaways, team, times tied, total, under, wins
SimpleSearch Tips
Tips on Asking Questions:
1.) Commas save lives: Lets eat, grandma. Lets eat grandma. Two very different things. Use of commas:
Houston when not a dog coming off a home game
This means Houston is neither a dog nor coming off a home game.
Houston when not a dog, coming off a home game
This means Houston is not a dog and is coming off a home game.
2.) Be precise, literal, and don't assume.
How have the Bengals have done after having won 4 of their last 5 games?
This means how have the Bengals done after having won exactly 4 of their last 5 games. If they won 5 of their last 5 those instances would not appear in your results. If you want know how the Bengals have done after having won AT LEAST 4 of their last 5 games, specify it.
3.) Try to write proper English in a tangible complete sentence.
If you misspell words or don't articulate yourself clearly you're increasing the chances that you won't be understood or get the answer you're looking for. Don't hesitate to ask a question in our Discord Community if you're unsure.
Notes:
1.) We've tested the language learning model to be over 95% accurate at translating English, especially for simpler inquiries, and with its machine learning algorithms
it will only continue to improve. Be aware that SimpleSearch may not understand you or properly translate 100% of the time dependent upon how articulate and concise your question is.
Give your search results a Thumbs Up or Thumbs Down to help it learn. If you don't think it gave you the right answer, let it know. Conversely, if it looks correct, also let it know.
2.) SimpleSearch is not trained on player specific queries, yet.
3.) SDQL itself currently still provides more versatility for detailed searches like open ended queries, list searches, and custom table queries.
4.) SimpleSearch is currently available for NFL and NBA and we are actively working to expand its availability to all other sports.
