PT4 Database Schema

[WhiteRider]

This:

cash_hand_summary.str_actors_p LIKE '_%0%'

..includes any time that the button acted after at least one other player acted, so includes any hand where the button raises then calls (amongst many other combinations).
To specify that the first player to act was not the button (i.e. that someone limped first) you'd be better just checking that the first character is not '0'.
e.g.

cash_hand_summary.str_actors_p NOT LIKE '0%'

[Mr Tiger]

WhiteRider
Works! That was easy Ty very much!

[Mr Tiger]

Has columns limit (1600) changed?

[kraada]

Since PT4 custom stats are not cached there is no limit to the number of columns you can create.

[Mr Tiger]

Hmm... Then I have a question. I have a lot of imported from PT3 custom stats (many will be deleted) and now creating new PT4 stats. Recently I was not able to duplicate a column (duplicate button was grayed out). I deleted some columns and was able to create new ones again.

[kraada]

I'll ask to see if there's a hardcoded limit for you; the limits in PT3 were due to PostgreSQL and are no longer a concern in PT4.

[kraada]

I've been told there is a limit in PT4 but it is a bit softer than the PT3 limit -- you'll have 1592 columns to work with.

[sawwee]

I have more than 1600 custom columns in my PT4 and I'm still able to create new columns.
(However postgres is not able to handle more than 1664 columns queried in 1 query, so if you want to use all the columns in the same HUD that might be a problem. I hope soon PT4 developers will split the queries to ask for only those columsn which are needed for the exact popup the player clicked on.)

[PropokerHUDs]

I have more than 1600 custom columns in my PT4 and I'm still able to create new columns.
(However postgres is not able to handle more than 1664 columns queried in 1 query, so if you want to use all the columns in the same HUD that might be a problem. I hope soon PT4 developers will split the queries to ask for only those columsn which are needed for the exact popup the player clicked on.)

Same and agree...

[Mr Tiger]

Please, explain me some more fields:

1) cash_hand_player_statistics.amt_p_4bet_facing
Does "cash_hand_player_statistics.amt_p_4bet_facing>0" mean the player faces exactly 4bet (not 4bet+)?

2) cash_hand_player_statistics.amt_p_5bet_facing
This includes 5bets+, right?

3) cash_hand_player_statistics.amt_f_bet_facing
This includes exactly flop bet (not raise, reraise or so), right?

4) cash_hand_player_statistics.amt_f_4bet_facing
This includes flop 4bet+, right?
-----------------------------------------------------------------------------------------------------------
5) cash_hand_player_statistics.amt_f_bet_made
"cash_hand_player_statistics.amt_f_bet_made>0" means the player makes a simple flop bet or it means the player invest some money on the flop or something another?

6) cash_hand_player_statistics.cnt_players_lookup_position
cash_hand_summary.cnt_players_lookup_position
What does these fields mean?