databases from PT3 beta "lost" in retail version

[BillyTheBull]

I recently purchased the full version of PT3 after using the various beta versions for the last couple of months. My question is, what happened to the dbs from the betas -- there are at least two of them, maybe three, "out there" somewhere -- and how can I either merge, delete, or purge them from my computer? In one of them I manually (=painstakingly) entered tournament results for at least 50 tourneys or so, and I'm a little pi . . . disappointed to have lost all that information once I purchased the retail version. . . .

[keggler]

have you just downloaded the retail version without postgres? this download should install and leave your existing db's intact, so you can just connect to them.

you could then create a new db say, connect to your old ones, export the hh's & results from these, then re-import to your new db.


susan

[WhiteRider]

Keggler is right, on the Database Management screen, click New and then check "This database already exists" and browse to it.

[BillyTheBull]

Keggler is right, on the Database Management screen, click New and then check "This database already exists" and browse to it.

What if I just went with the defaults and let the PT3 retail version (w/out PostGre) set up a whole new DB? Am I SOL? Or can I still go and find/combine, or at the very least delete the old DBs from the Beta version(s)?

[bugsbunny]

If you installed the version without Postgrse those old DB's are (or at least should be) still there.

Start PT3. Go (on the menu):
Database|Database Management
Click New
Check "This database already exists" and then click "browse"
Any databases compatible with the current version of PT3 should then show up (including the current one). Select one, give it a descriptive name (or leave the default).
Click connect.
Repeat for any others.
The Database Management window also allows you to change the default DB, as well as the active DB. You can also change the active DB via Database|Set Active Database

The HUD can be set to read from multiple DB's, so it will pull stats from whatever DB's you tell it to. You can't really combine the DB's into one though, unless you export hands from one and then re-import into another.

The Database Management screen will also allow you to delete DB's you no longer want.

[BillyTheBull]

Thanks, bugs!

I was able to find all my old DBs, export everything, create a brand-spanking new DB, and re-import everything. Now I'm basically ready to get rid of the old DBs, but there's one last thing that I'm missing, and that's all the tournament results I painstakingly entered into one of my old DBs at one time; is there any way at all to transport this info into my new DB? I have over 150 tourneys in there now with absolutely no results, and I think I manually put in at least 50-70 results into the older DB, so this would save me a significant amount of work, time, and aggravation.

By the way, I thought about just making the old DB with the tourney results my default and import everything into that one, but PT3 complains that "This is an older database, please create a new one." or something to that effect whenever I make it active.

Any suggestions?

[keggler]

the thing is, if you just exported hh's you wouldn't have gotten the tournie summaries...

if you've still got the old db's, then use the native postgres pg_dumpall and psql commands to back them off & restore in their entirity -

IT WOULD BE PRUDENT HERE TO CREATE ANOTHER BRAND NEW DB FOR THIS PURPOSE FOR NOW AND USE THAT ONE FOR THE RESTORE; JUST SO YOU CAN PROVE TO YOUR SATISFACTION EVERYTHING'S BACK THE WAY YOU EXPECTED IT TO BE... before wacking the redundant db's...


this should bring the lot back,including your manually entered summaries...


susan

[WhiteRider]

if you've still got the old db's, then use the native postgres pg_dumpall and psql commands to back them off & restore in their entirity

Wouldn't this just recreate the database in the old format?
The point of the message telling you that it's an old database is that the structure of the database has now changed so you need to use one created in the correct structure.

Exporting from the old database should include the tournament summaries, although I'm not sure that it's working correctly at the moment.
In the folder you exported the old DB to, are there files with names that suggest tournament summaries?

[keggler]

if you've still got the old db's, then use the native postgres pg_dumpall and psql commands to back them off & restore in their entirity

Wouldn't this just recreate the database in the old format?
The point of the message telling you that it's an old database is that the structure of the database has now changed so you need to use one created in the correct structure.

dave,

As a general rule, the internal data storage format is subject to change between major releases of PostgreSQL (where the number after the first dot changes). This does not apply to different minor releases under the same major release (where the number after the second dot changes); these always have compatible storage formats. For example, releases 8.1.1, 8.2.3, and 8.3 are not compatible, whereas 8.2.3 and 8.2.4 are. When you update between compatible versions, you can simply replace the executables and reuse the data directory on disk. Otherwise you need to back up your data and restore it on the new server. This has to be done using pg_dump; file system level backup methods obviously won't work. There are checks in place that prevent you from using a data directory with an incompatible version of PostgreSQL, so no great harm can be done by trying to start the wrong server version on a data directory.

It is recommended that you use the pg_dump and pg_dumpall programs from the newer version of PostgreSQL, to take advantage of any enhancements that might have been made in these programs. Current releases of the dump programs can read data from any server version back to 7.0.

i believe the OP had databases from previous betas - they would've all been created in postgres 8.n.n? so the postgres native commands should work...


susan

[WhiteRider]

I'm not talking about the postgres versions, I'm talking about the fields within the database, that PT3 creates.
Databases created by PT3 after the commercial release have some different fields than those before, and I assume that dump/restore will just recreate the database as it was originally built, so it would still have the old fields and not the new ones, therefore it would still be an "out of date" database as far as PT3 is concerned.
The only way [I know of] to get the data/hands from an out of date DB into a correctly structured one would be to export the hands from the old DB, create a new one, and import the exported hands.