Ajeetav Nayak wrote:cash_hand_player_statistics.enum_p_3bet_action = '4bet'
The action a player takes when facing a 3bet is either fold (F), call (C) or raise (R) so if they 4bet that would be:
- Code: Select all
cash_hand_player_statistics.enum_p_3bet_action = 'R'
however you do not need to use this at all because you have already specified in the aggressors string that the player in seat one 4bet with:
- Code: Select all
cash_hand_summary.str_aggressors_p = '8101'
although this needs changing as if the hand gets 5bet the hand will not be counted because you are limiting the aggressors string to 4bet hands only. If you want to inlcude possible future actions you can use:
- Code: Select all
cash_hand_summary.str_aggressors_p LIKE '8101%'
A similar change will also be needed for the other strings to account for future actions. For example your opportunities column isn't going to count any hands that do get 4bet as you've specified the aggressors string is only '810' and the actors string is '10'. For more information on pattern matching in PostgreSQL see
this guide. You can also use pattern matching to include/exclude other scenarios. For example the current actions column excludes the blinds from calling in-between so assuming you don't want to count those hands you would need to account for that in the opportunities column as well.