Page 1 of 3

SQL command bug

PostPosted: Mon Apr 28, 2008 4:43 pm
by Timmehhh
An expert said in post #1778 on the Pokertracker 3 thread on 2+2 forums that this was a bug.
http://forumserver.twoplustwo.com/showt ... 44&page=20

How can I get my PT3 to work?

Image[/QUOTE][/QUOTE]

Kind regards Timmehhh

Re: SQL command bug

PostPosted: Mon Apr 28, 2008 5:03 pm
by WhiteRider
Try putting the User back to "postgres". This is the default value IIRC.
This is the database connection user, not your poker username. or whatever.

Re: SQL command bug

PostPosted: Mon Apr 28, 2008 5:15 pm
by Timmehhh
WhiteRider wrote:Try putting the User back to "postgres". This is the default value IIRC.
This is the database connection user, not your poker username. or whatever.

No, I already logged in. I have an old postgresql from PT2 were my user =Timmehhh
Please read the post on the 2+2 forum from a PT3 developer.

Re: SQL command bug

PostPosted: Mon Apr 28, 2008 5:17 pm
by WhiteRider
OK, then I'll leave it to the postgres experts...

Re: SQL command bug

PostPosted: Mon Apr 28, 2008 9:40 pm
by Josh
This is a bug due to the case sensitivity of the user name. It will work once the bug is fixed.

Re: SQL command bug

PostPosted: Tue Apr 29, 2008 7:21 am
by Timmehhh
Josh wrote:This is a bug due to the case sensitivity of the user name. It will work once the bug is fixed.

I just have to wait for PT3 beta 10?

Re: SQL command bug

PostPosted: Tue Apr 29, 2008 7:43 am
by Josh
I hope to have this fixed in beta 10, yes.

Re: SQL command bug

PostPosted: Tue Apr 29, 2008 9:29 am
by Timmehhh
Josh wrote:I hope to have this fixed in beta 10, yes.

Okay thanks 8-)

Re: SQL command bug

PostPosted: Sun May 04, 2008 6:30 am
by Timmehhh
Not working in beta 10 yet :cry:

Re: SQL command bug

PostPosted: Sun May 04, 2008 5:31 pm
by Josh
No, sorry. I haven't had a chance to get to it.

highfalutin