PFortune wrote:Now in order to have any shot of doing this I'd need to actually know what the pt4 database is and what it looks like, then there'd be a chance of me being able to work out what to do
So if this subqueury is too complicated to be provided, where can I find documentation on how th pt4 database is made and what the tables look like. Unfortuntely without this I can't apply the knowledge in the link about select you mentioned and I'm not coding savvy enough to infer the nature of the database from that one example you gave
Also a table of what these definitions are what they mean would be great.
We have not
published the schema like we did for PokerTracker 3 however the meaning of database fields haven't changed in any significant way. Also forum member 'Bininu' made their own schema document for PokerTracker 4 available in
this thread.
PFortune wrote:Could you help me understand what the following are referring to?
tourney_hand_player_statistics.id_hand
in
I am not an SQL expert but basically when querying something that's not directly stored in the data for the player you are creating the statistic for then that needs a subquery to test from all the other players perspectives to find the data from hands that meet your desired criteria.
PFortune wrote:The difference between tourney_hand_player_statistics and thps
thps
tb
tourney_blinds tb
thps is an abbreviation of
tourney_hand_player_statistics.
tb is an abbreviation of
tourney_blinds.
PFortune wrote:I have no idea how to refer to the person making the 2bet
If a player makes a 2Bet the following is true:
- Code: Select all
tourney_hand_player_statistics.flg_p_first_raise
A subquery that tests the effective stack of a player on the button making a 2bet would look like this:
- Code: Select all
tourney_hand_player_statistics.id_hand in (select thps.id_hand from tourney_hand_player_statistics thps, player p, tourney_blinds tb where thps.id_player = p.id_player and thps.id_blinds = tb.id_blinds and thps.position = 0 and thps.flg_p_first_raise and (thps.amt_p_effective_stack / tb.amt_bb between x and y))
where 'x' and 'y' are the lower/upper boundaries of the players effective stack in big blinds.