notetracker problem?

[mkjmkjmkj]

notetracker doesnt work i think it is after i updated but not totally sure since i havent played for two months

i get this error message when i test the notes so if you have any idea what kind of custum note that is causing the problem so i can remove it.

Unable to execute query: SELECT (cash_hand_player_statistics.id_player) as "__can__id_player", (cash_hand_player_statistics.id_limit) as "__can__id_limit" FROM lookup_actions lookup_actions_t, lookup_actions lookup_actions_f, cash_hand_player_statistics , cash_hand_summary WHERE (cash_hand_summary.id_hand = cash_hand_player_statistics.id_hand AND cash_hand_summary.id_limit = cash_hand_player_statistics.id_limit) AND lookup_actions_f.id_action = cash_hand_player_statistics.id_action_f AND lookup_actions_t.id_action = cash_hand_player_statistics.id_action_t AND ((cash_hand_summary.id_hand=470017 AND (cash_hand_player_statistics.id_player=5716 OR cash_hand_player_statistics.id_player=23035 OR cash_hand_player_statistics.id_player=23130 OR cash_hand_player_statistics.id_player=23131 OR cash_hand_player_statistics.id_player=23134 OR cash_hand_player_statistics.id_player=23143))) AND ((((((cash_hand_player_statistics.flg_p_first_raise and cash_hand_player_statistics.flg_p_open_opp)))))AND ((NOT (((((cash_hand_player_statistics.flg_p_3bet_def_opp)))))))AND (((((cash_hand_player_statistics.flg_f_cbet_opp)))))AND (((((cash_hand_summary.cnt_players_f BETWEEN 2 and 2)))))AND (((((cash_hand_player_statistics.position BETWEEN 2 and 3)))))AND (((((cash_hand_player_statistics.amt_t_bet_facing > 0 and cash_hand_player_statistics.flg_f_cbet_opp and lookup_actions_f.action = 'X' and cash_hand_player_statistics.flg_f_cbet) and not(cash_hand_player_statistics.flg_t_open_opp) and lookup_actions_t.action = 'F')))))) ; Reason: Fatal Error (ERROR: syntax error at or near ")" LINE 1: ...ics.flg_t_open_opp) and lookup_actions_t.action = 'F'))))))

[kraada]

It looks like this is a note where you have players who:
Raise First In, don't face a 3bet, have a chance to cbet in a heads up pot, while either in the HJ or the position before that (at 6max, that'd be UTG), face a turn bet from someone out of position, checked through the flop, but made a flop cbet, and folded on the turn.

This note will never return any hands because you can't check through the flop and face a turn bet.

Making that a little simpler, it looks like you may have turn probe set as well as cbet flop which can never happen in the same hand.

[mkjmkjmkj]

it seems that any custom note that has fold to turn probe bet is causing a problem.

and the only condition for one of the notes is fold to turn probe so im sure thats the problem.
and im sure it wasnt a problem before i updated.

[kraada]

I'll take a look into that filter. Do you have anything in the Opponent section?

[mkjmkjmkj]

no there is nothing in opponent filter
the only filter is fold to turn probe in the player filter

[BillGatesIII]

Somehow, the parser puts

Code: Select all

and cash_hand_player_statistics.flg_f_cbet)

into the expression when translating Folded to Probe Bet (turn only, river works ok). If that line is deleted (including the closing parenthesis), the SQL will run fine again.

[kraada]

Please restart PT4 using the logging enabled link on your Start Menu, reproduce this problem and then report it via our support system with the log file - that will help us figure out what is going on here and get it fixed for you. You can find that file by clicking File --> Show User Data Folder in the main PT4 window - the file we need is the text file called PokerTracker4 that is in that folder. That's definitely not in the actual filter so we'll need to figure out what's causing the parser to do this in this particular case so what we can get it fixed.

[BillGatesIII]

Tikcet 140694.

[mkjmkjmkj]

is there already sent a support ticket from bill gates or should i do it too?

[kraada]

We've isolated the problem and will get it fixed; if you'd like automated notification when a fix is available, please create a ticket as well and ask to be linked to Bug # 4912.