![]() |
|
#11
|
|||
|
|||
|
[ QUOTE ]
Another issue: So I recently REPLACED a DB on my laptop with one of the very same name. E.g. I had postgres database XYZ on my laptop, then used the SQL Database functions window in PT to delete it completely, and copied over a NEWER version of that same XYZ DB from my desktop (which i use to mine). So essentially I simply replaced the DB with one of the same name, but with 200,000 or so new hands in it. But I fire up PTAGG, expecting it to start importing all the new hands, but it doesn't seem to recognize that there's a whole batch of new hands (albeit in the DB of exactly the same name.) Is there a way to get it to recognize these new hands? [/ QUOTE ] Based on what you describe, PTAgg *should've* found the new hands and imported them. It stores a "Last GameID" for each database, and checks to see when it goes higher. Maybe if for some reason that 2nd database you had started at a higher GameID? That would be strange though, I can't think of a case that would cause that. I've heard other reports that PTAgg doesn't always import new data, so its something I'm looking into. When I find something I'll let everyone know. Also, if you notice any obvious patterns in something that causes it please let me know too. -Ben |
|
|