1600 limitation - cash/tourney separate or combined?

[ChicagoAl]

Hi guys.

I've been doing quite a bit of custom stat development, and I'm starting to worry about the column limitation. Is the 1600 limit all custom columns, or per database? In other words does it count HE cash and HE tourney separate, or are they all combined (giving me an effective 800 column limit if i am using them on both sides)?

Also, which table in SQL are the custom columns stored in so I can check how many I have now (or is there another mechanism for checking)?

Thanks!

Al

[WhiteRider]

I'm pretty sure that the restriction hits in the cache tables, as custom "columns" aren't actually in the database until the cache is built, so the limit will be on each game type.

[kraada]

For the record, the columns are stored in the holdem_cache, tourney_holdem_cache, omaha_cache, and tourney_omaha_cache, depending on the game type you are playing.

[ChicagoAl]

Thanks guys. And is the limit 1600 TOTAL columns per cache database or 1600 CUSTOM columns per cache database?

[kraada]

1600 columns total per cache table - there is a hard limit on 1600 columns for any PostgreSQL table. The limitation is PostgreSQL's, not PT3's.

[ChicagoAl]

Thanks Kraada.

Not to give away too much of what I'm thinking, but it looks like the custom columns are all being created as "integer". Is there a way to use a different data type (bigint, text, or even better array) for a custom column?

Al

[kraada]

I see where you're going with it and I'd love to have that ability too unfortunately it is not possible at this point in time.

[ChicagoAl]

Can't blame a guy for trying :-)