i quoted myself since u might have overlooked it and i still witness those things in the current version:
[ QUOTE ]
i looked through your program and database and noticed that you "cut" partypoker HHs wrong: theres always the "Game #5609898428 starts." and "#Game No : 5609898428" lines at the end of a stored HH, but this stuff actually belongs to the next hand [img]/images/graemlins/smile.gif[/img]
another thing:
with party poker handhistories you might want to get rid of all ">You have options at Table XYZ.." lines before storing them in your DB!
i had to write my own program to do this on ptrackers existing databases.
[/ QUOTE ]
also the postgres logs still warn:
[ QUOTE ]
2007-07-25 22:29:37 WARNING: nonstandard use of \\ in a string literal at character 63
2007-07-25 22:29:37 HINT: Use the escape string syntax for backslashes, e.g., E'\\'.
....
2007-07-25 22:23:14 WARNING: nonstandard use of escape in a string literal at character 94
2007-07-25 22:23:14 HINT: Use the escape string syntax for escapes, e.g., E'\r\n'.
[/ QUOTE ]
see
http://www.postgresql.org/docs/8.2/s...ompatible.html under "escape_string_warning (boolean)". the default for this setting is "on", so everyone should have these warnings in their log.
FIX:
[ QUOTE ]
Applications that wish to use backslash as escape should be modified to use escape string syntax (E'...'), because the default behavior of ordinary strings will change in a future release for SQL compatibility.
[/ QUOTE ]
also, the total hands of the report by game buyin (for my screenname) still (slightly) differ from the handcount i get from the players tab when filtering for everyone with >2k hands.
another thing i noticed in the postgres log while importing party HHs is this:
[ QUOTE ]
2007-07-25 22:09:50 ERROR: invalid byte sequence for encoding "UTF8": 0xe4e46b
2007-07-25 22:09:50 HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding".
[/ QUOTE ]