Quote:
Originally Posted by Mr_Snood
Yes. Currently one should create a new database for every different struct.
Thus having a database for "heads up" and a seperate database for "6 max"...
Yes, this is one option, and the only one available at the moment. I play full ring, six max, and some heads up as well as datamining a LOT.
Having multiple pt3 databases is a huge pain! In the pt3 forums, pat has suggested to only have ONE db. (ok, actually possibly two, one for played hands, and one for observed hands)
Having multiple dbs is a massive pain in the bottom. They must be added to separately, analysed and clusted. And if you accidentally add hands to the wrong database you are totally stuffed!
[QUOTE=Mr_Snood;3310597]
Yes, to resolve this one needs a "simple" modification of the WHERE clause.
But i need to analyse the database structure to find this modification.
So if you know what to put in the WHERE clause you could save me a lot of time. Time that i am currently lacking of...
And i need to do this for every database that SpadeEye supports (PT2, HM, PO, PT3)...
Another thing is to put up a userinterface for such a "playercountfilter"...
Can anyone out there help Mr Snood with this?
If we could just have a little tab, so we choose how many people were in the hand (ie hu/5-7, 7-10), this would be brilliant!