The postresql build dependency psycopg2 isn't listed in the walkthrough but I assume you have it already installed (I used http://www.stickpeople.com/projects/....3-release.exe) This is listed in the next walkthrough update. If you want to be certain, install this dependency and do a quick rebuild of the exe.

Good to know you got the script to work ok

hi

ive installed v0.20 and already successfully imported HH. However, there are many points in the menu (like "maintain databases" and many more) which have a "todo" comment and when i click on them i get a message that it is "unimplemented". I have no idea what to do now and coulnt find an answer on the support sites yet.

Thanx for your help and respect for the job you did

It simply means that those menu items don't do anything yet. They indicate features that might be added later on if and when the developers have the time.

ok, ty

What's new about fpdb-0.20pre3.exe version which was posted on 6/26?

How is it different from fpdb-20100614-exe.exe version that i have right now?

Thanks

Not hugely different:

o/ Technical changes to upgrade the underlying packages (Python 2.5->2.6)
o/ Fixes for lockups when task switching to/from fpdb
o/ Fixes for lockup when closing fpdb with the hud open
o/ New stats: Aggression factor, fold street percentages, overall CB

I just cloned your repo and I'm still getting this error for games with:

Ignore this, git fail.

How do i go about doing this? Do i need to recreate tables?

For ubuntu users: a new snapshot package (python-fpdb_0.20~git20100630_all.deb) is available. It should work directly on debian unstable too, as both these systems now default to python 2.6.

Yes, recreate and re-import.

I just recreated my database because some tournaments slipped in by mistake. I don't want to waste the space for the few I play.

That brought mind... in bytes, what is the point that sqlite starts to slow down. I noticed it grows fairly fast each day. I had well over 200megs in the fpdb.db3 file when I deleted it. BTW, I still can't "recreate" in the program itself. I have to close the program (no big deal), delete fpdb.db3, then reopen the program to an empty db and import my saved files.

I'm running the 0605 version, NOT the exe version. If that's a fix in a more recent NON-exe version I'll just wait. Is it?

Thx
Dog

I may have found my own answer. I Googled it. From what I gathered, the db is made up as "pages" with a default of 1k per page. And, the max pages was a tad over a gig (1,000,000,000)

If both those statements are true... then it's 1,000,000,000 X 1,000 which = pretty big

Actually, 1,000,000,000,000 which is basically a terabyte, that's bigger than my harddrive. So, it seems hd size will come into play before what they say, "66% is starting to push it a tad" and slowdown may start to occur... Hey, techies... does that sound roughly about right?

That being the case, it shouldn't show any side-effects till I hit about 660gigs in the file... duh, my hd is only 300gig, so I guess I'm fairly safe, unless a more knowledgeable developer says, "what are you... an idiot"

Dog

An updated fpdb Windows preview is available. Version is fpdb-0.20pre4.

http://sourceforge.net/projects/fpdb/files/

New for this version:

• Carbon/BlackChip poker update for timestamps in hand histories
• Postresql has been built-in to the exe (not tested)
• Several more task switching fixes
• Warning on startup about "sets being deprecated" no longer happens
• Graph "export to file" now works
• popup warning message on fpdb closedown is no-longer displayed

Known issues:

• Exported Graphs sometimes have a solid black border, reason unknown
• Directory chooser for exported graphs selects a sub-directory by default
• A HUD Lockup on the previous build -pre3 was reported, circumstances unknown.

Feedback and bug reports welcome.



gimick/

I don't think its quite that simple unfortunately, because other things than sqlite are involved. However, if you have less than say 100k hands in your database it's not a problem. I don't know how fast fpdb is on even bigger DBs but it does scale really well so far.