tag:blogger.com,1999:blog-7415921575638169343.post88143346823438299..comments2009-07-09T15:34:19.009+02:00Comments on The Poker Copilot Blog: A Brief History of Poker Tracking SoftwareSteve McLeodhttp://www.blogger.com/profile/14821039898589441072noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7415921575638169343.post-86862231928145644032009-07-09T15:34:19.009+02:002009-07-09T15:34:19.009+02:00I heard there was some PostgreSQL-bashing going on...I heard there was some PostgreSQL-bashing going on here...<br /><br />:-)<br /><br />No. In this one obscure little domain (hand history tracking) I prefer PostgreSQL but in general I'm a MySQL fan. Who doesn't like MySQL? Seriously.James Devlinhttp://www.codingthewheel.comnoreply@blogger.comtag:blogger.com,1999:blog-7415921575638169343.post-55358261856193467622009-07-08T23:55:18.389+02:002009-07-08T23:55:18.389+02:00I'd like to ask, in the friendliest possible w...I'd like to ask, in the friendliest possible way, why Poker Copilot isn't using MySQL or (shudder) Postgres? Yes, my 'nix and net AMP roots are showing, I very much prefer MySQL to Postgres. Either one would enable me to very easily query my data and answer the questions running through my brain, such as "How much has it cost me to play KJ from middle position in fixed limit cash games?" <br /><br />Of course I also wonder how many times faster it would be to use MySQL rather than a java db which is a couple of layers removed from OS level speeds. Would it speed things up ten times? Or more? <br /><br />Enquiring minds want to know ;-)KeithXhttp://www.blogger.com/profile/05956175169903906369noreply@blogger.com