Page 5 of 5

Re: Hole card lookup values

PostPosted: Wed Apr 16, 2014 7:47 am
by js2002
This expression doesn't validate in stats:

"tourney_hand_player_statistics.id_holecard in (41,42)"

The comma is the problem. How do I escape it? I'vo got whole ranges, so I cant do this:
tourney_hand_player_statistics.id_holecard in (41) OR tourney_hand_player_statistics.id_holecard in (42)

In the logfiles an exp like this works: tourney_hand_player_statistics.id_holecard in (41,43,62,64,81,83,98,100,113,115,126,128,137,139,146,148,155), but not in stat column :-(

Re: Hole card lookup values

PostPosted: Wed Apr 16, 2014 10:05 am
by kraada
There is a known issue with commas in column definitions at this time and, sadly, there is no known workaround.

Re: Hole card lookup values

PostPosted: Wed Apr 16, 2014 10:28 am
by js2002
So is there a problem when I put 169 terms into a column?

Re: Hole card lookup values

PostPosted: Wed Apr 16, 2014 11:01 am
by kraada
The problem is, as you pointed out, the comma. As I said, there is no known workaround. I don't know off the top of my head if there is a maximum column size.

Re: Hole card lookup values

PostPosted: Wed Apr 16, 2014 12:35 pm
by js2002
If I use 169 term, I dont need any comma.

Re: Hole card lookup values

PostPosted: Wed Apr 16, 2014 2:28 pm
by kraada
kraada wrote:I don't know off the top of my head if there is a maximum column size.

highfalutin