Beta 3.07.2 Install Issue

PostgreSQL is the database server used to store information. Do you have a question or are you having problem with PostgreSQL? If so, post them here.

Moderator: Moderators

Re: Beta 3.07.2 Install Issue

Postby kraada » Sat Jul 31, 2010 3:35 pm

Downgrade to 3.06.2 (available on our download page, then open that version. Create a new database there, and set it as active and default and then upgrade back to 3.07.2 and that database should upgrade successfully and you should be able to get into PT3 then.
kraada
Moderator
 
Posts: 54431
Joined: Wed Mar 05, 2008 2:32 am
Location: NY

Re: Beta 3.07.2 Install Issue

Postby Yazalde » Mon Aug 02, 2010 2:49 pm

It works...

Thanks
Yazalde
 
Posts: 5
Joined: Fri Jul 30, 2010 9:53 pm

Re: Beta 3.07.2 Install Issue

Postby Russelldust » Fri Aug 06, 2010 6:43 am

kraada wrote:There is actually nothing left of the old system to convert. However, the process of updating the databases is now made much easier with our new system - please see the new Tutorial: Tournament Auto Detection for details on how to utilize the new system. It should not take long to get things back to a very similar state to what you had previously.

I've looked at the tutorial but I still don't understand what is the best thing to do about all my 'lost' tournament types.

Are you saying: it is not possible to recover my scores of hours of painstakingly selected tournament types; but I don't NEED to do that, because PT can now 're-detect' the tournament types automatically?

Are you, in a sense, saying: I've wasted all that time manually entering tournament data, because PT can now do it automatically, and accurately?

:? Or have I misunderstood?

If that is what you are saying, well, I'm a little skeptical about letting PT run loose on all my existing data. Please let me elaborate...

:geek:

After a typical day/week of tourneys, I would import a batch of HHs into PT and go through all my new tourneys in the Enter Tournament Results dialogue.


:club: 1. PT used to get loads of the buy-ins wrong. (For example: I play a large volume of $21.50+1.50, $43+4, $64+6 and $160+12 tournaments on PartyPoker. However PT used to 'guess' the buy-ins to be $20+3, $40+7, $70+0, and $100+72 (lol) respectively. Granted, the hand histories just indicated the total buy-ins of $23 / $47 / $70 / $172, so I can understand that PT had to 'guess'.)

So my first concern is that if I let PT 're-detect' all my tourneys, all my tourney buy-ins will be un-corrected again - hours and hours of work lost?!


:club: 2. Further, I manually classified all my tourneys, for example as 6-Max Rebuy, Rebuy Satellite etc... Now, in principle I welcome the revised system (no need for people to create their own tourney types). But I simply don't understand how PT is going to 'recover' all my hours and hours and hours and hours of work, where I set the tourneys types manually? (and with 100% accuracy!!)

For example, can PT now actually detect whether my $25+2.50 iPoker rebuy tourneys were six-max or ten-max?
Can PT now recognise a $47 PartyPoker satellite and classify it as a $43+4 Turbo Satellite versus a $43+4 Satellite?

I've looked at the tutorial you linked to, but I simply don't see how PT is going to guess all the tourney types correctly? TBH some of the classifications are a bit subjective anyway (e.g. I somewhat arbitrarily decided to put 'speed rebuy sats' and 'speed sats' under the same classification of 'speed sats', rather than have an excessive number of sub-classifications).


:club: 3. And can you guarantee me that this auto-update process won't 'lose' my manually-entered tournament data, such as number of entrants, finishing positions, and number of rebuys/addons? PT has a history of obliterating this data, particularly for Party tourneys, where I re-import hand histories for already-imported tourneys.

For example, wherever I imported the final HH for a given Party tourney (which included the line 'Hero_Screen_Name has finished in Xth place'), if I had already imported that tourney before, and had already entered my number of rebuys/addons, PT would actually reset my rebuys/addons to zero upon re-importing that HH!


:ugeek: Re point 2: isn't there some SQL command I can run to search for all tourneys with the 'old tourney type' of X, and change them to a certain corresponding tourney type under the new system? That way, I could be sure that all my existing tourneys were classified with 100% accuracy.

I have thousands upon thousands of tourneys in my database, and although it was extremely tedious that I used to have to select all the tourney types manually, at least I've done all the hard work now, and got it 100% right.


Please advise! :?

I'm not change-averse - I honestly do welcome the new system! - I'm just concerned that I might have lost a vast amount of prior work.
Russelldust
 
Posts: 106
Joined: Thu Jul 24, 2008 2:51 am

Re: Beta 3.07.2 Install Issue

Postby WhiteRider » Fri Aug 06, 2010 9:05 am

Russell - before you do anything, make a Backup of your database.

In 3.07.2 the way that tournament table types are stored has been changed - the old types are not used anymore, and the table they were stored in doesn't exist.
When you update to 3.07.2 the old types were converted to the new format, but only the known types - PT3 doesn't know what you have added to the database yourself. Therefore any types you added yourself will be lost.

The new detection mechanism uses as much of the information from the hand history files as possible to determine the table type, results, etc. Depending on the type of tournament this may be very accurate, or not. For instance STT results can be determined precisely even if the finishing positions are not recorded because we can see the order that players were knocked out, but that can't be done for MTTs.
The length of blind levels is used to determine Turbo and Super Turbo (about 5 minutes or about 3 minutes).
6 max (etc) tag will be added automatically based on table size.
Rebuy will be added if rebuys are detected or mentioned in the HH, similar for satellites and other tags.

The detection mechanism will not overwrite any non-zero (manually entered or imported) values, so your finish positions and prizes will not be changed.
You can choose whether table types will be changed using the "Protect Filled Table Type" option (Tournaments > Enter Results > Auto Detect) - if that option is on then the type will not be changed unless it is N/A.

This mechanism should get the table types right, but since the mechanism is pretty new some types may not be correct - we're updating the rules all the time, though.
What I'd suggest you do is either:
- make a backup of your database and experiment in your real database, with the option to revert to the backup.
- create a new database and import some of your tournaments to it and experiment there. If you like the results you get then run the detection in your main DB.

If you want to see how a tournament will be classified you can run Auto Detect with the Protect Filled Table Type on and it will tell you what type it thinks it is, but not actually change it.

I don't know whether all the buy-ins and rakes are "guessed" correctly by PT3, but if you have any which are imported incorrectly in 3.07.2 then please attach them to a Support ticket and tell us what the correct buyin and rake are and we'll get them updated. (Or just send us a selection with the correct values and we'll test them.)

I can't promise that it will get everything right, but please let us have any that aren't and we'll see if the rules can be improved to handle them correctly.

For example, wherever I imported the final HH for a given Party tourney (which included the line 'Hero_Screen_Name has finished in Xth place'), if I had already imported that tourney before, and had already entered my number of rebuys/addons, PT would actually reset my rebuys/addons to zero upon re-importing that HH!

This is fixed for the next release.
WhiteRider
Moderator
 
Posts: 54018
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Previous

Return to PostgreSQL [Read Only]

Who is online

Users browsing this forum: No registered users and 5 guests

cron