lookup_actions

[ChrisD]

Does the information in this table change from release to release, or is it just populated on the fly? I had kind of a hair pulling bug hunt when I found that my tourney_luck calculator wasn't working because these values changed from one database to the next...

old:
0;"''"
1;"F"
2;"R"
3;"C"
4;"B"
5;"CF"
6;"X"
7;"XC"
8;"RC"
9;"RF"
10;"CC"
11;"XF"
12;"BC"
13;"XR"
14;"BR"
15;"XRC"
16;"BF"
17;"RR"
18;"CR"
19;"BRC"
20;"XRR"
21;"XCF"
22;"XCC"
23;"XCR"
24;"CRC"
25;"XRF"
26;"RRC"
27;"CCF"


new:

0;"''"
1;"C"
2;"F"
3;"R"
4;"X"
5;"B"
6;"CF"
7;"XF"
8;"XC"
9;"RC"
10;"RF"
11;"CC"
12;"RR"
13;"XR"
14;"BC"
15;"BF"
16;"CR"
17;"XCF"
18;"BR"

[ChrisD]

Actually, probably to answer my own question, I guess that would make sense since PT3 can't really predict every possible action taken by someone (I get a giggle out of "CCF" - call, call, fold - I had to look that hand up just to see who was so bad they called 2 raises by someone else and folded to the 3rd).

The query I'm probably looking for is something along the lines of

select * from lookup_actions where substring(lookup_actions.action from length(lookup_actions.action)) = 'C'

[WhiteRider]

That table is populated on the fly as each action sequence is encountered.