Re: Automatic colors statistics
Posted: Fri Sep 02, 2016 7:34 am
(1) If you have the SQL skills to define things as needed in your own schema you are welcome to do so. It's definitely beyond the scope of our support here.
(2) There is a maximum of 1600 columns per PostgreSQL query. In effect this means the cache and any queries cannot exceed requesting 1600 columns - so you can cache about 1590 columns or so (there are some that are needed for identification), and in the HUD you cannot request more than 1600 cached and uncached columns for your HUD (which again results in about 1590 actual columns). There's no difference between a default stat or custom stat for the HUD's 1600 limit - it's about the columns and whether they are cached or not.
(3) With 7 players there is never a position 5 - see here for the mapping of numbers for each number of players. When 7 handed, there is one EP player - he is in position 4.
(4) I've never heard of anyone building anything this in depth so I can't estimate how long it will take to run.
(5) There isn't a maximum as far as I'm aware.
(2) There is a maximum of 1600 columns per PostgreSQL query. In effect this means the cache and any queries cannot exceed requesting 1600 columns - so you can cache about 1590 columns or so (there are some that are needed for identification), and in the HUD you cannot request more than 1600 cached and uncached columns for your HUD (which again results in about 1590 actual columns). There's no difference between a default stat or custom stat for the HUD's 1600 limit - it's about the columns and whether they are cached or not.
(3) With 7 players there is never a position 5 - see here for the mapping of numbers for each number of players. When 7 handed, there is one EP player - he is in position 4.
(4) I've never heard of anyone building anything this in depth so I can't estimate how long it will take to run.
(5) There isn't a maximum as far as I'm aware.