Re: keeping information about players around

2012-09-25 Thread Jean-Michel Pichavant
- Original Message - PHPMyAdmin? Might I ask why? This is a mud, so it's all command based, so that's not even a question, but I'm kind of curious how PHPMyAdmin factors in there. It's a database creation tool from all I've ever seen of it, to define tables. Also, using it requires

Re: keeping information about players around

2012-09-24 Thread Jean-Michel Pichavant
- Original Message - ytHello all: I've asked for a couple code reviews lately on a mud I've been working on, to kind of help me with ideas and a better design. I have yet another design question. In my mud, zones are basically objects that manage a collection of rooms; For

Re: keeping information about players around

2012-09-24 Thread Jean-Michel Pichavant
- Original Message - Pickle everything, use sqllite for your database. When you get things working, then you can start measuring your performances and think about clever implementation That was a bunch of information; sorry about that. what do you mean by using sqlite for the

Re: keeping information about players around

2012-09-24 Thread Dwight Hutto
I have yet another design question. In my mud, zones are basically objects that manage a collection of rooms; For example, a town would be it's own zone. It holds information like maxRooms, the list of rooms as well as some other data like player owners and access flags. The access flags

Re: keeping information about players around

2012-09-24 Thread Chris Angelico
On Tue, Sep 25, 2012 at 7:14 AM, Dwight Hutto dwightdhu...@gmail.com wrote: Also, If this is a browser app I'd go with phpmyadmin, and MySQL If a tkinter/wxpython/etc app, then maybe sqlite. Out of curiosity, why? MySQL isn't magically better for everything where data ends up displayed in a

Re: keeping information about players around

2012-09-24 Thread Dwight Hutto
On Mon, Sep 24, 2012 at 6:19 PM, Chris Angelico ros...@gmail.com wrote: On Tue, Sep 25, 2012 at 7:14 AM, Dwight Hutto dwightdhu...@gmail.com wrote: Also, If this is a browser app I'd go with phpmyadmin, and MySQL If a tkinter/wxpython/etc app, then maybe sqlite. Out of curiosity, why? MySQL

Re: keeping information about players around

2012-09-24 Thread Dwight Hutto
Out of curiosity, why? MySQL isn't magically better for everything where data ends up displayed in a web browser. No, but phpmyadmin is a great GUI for MySQL Meaning, it gives a great web app, that sqlite doesn't have...yet. It's the tools around MySQL for me, that gives it the umph it needs

Re: keeping information about players around

2012-09-24 Thread Chris Angelico
On Tue, Sep 25, 2012 at 8:31 AM, Dwight Hutto dwightdhu...@gmail.com wrote: And in the end it's usually html, php, css, javascript in the browser, atleast for me it is. I'm just starting to utilize python in that area, so excuse the naivety. In the browser it's HTML, CSS, JavaScript

Re: keeping information about players around

2012-09-24 Thread Dwight Hutto
is just a way of generating that. Any language works on the back end... and PHP isn't the best :) Python does quite well at that task; I have a tiny little Python script that uses a web browser as its front ent. This stems from my limited usage of python in the browser(I usually use it for

Re: keeping information about players around

2012-09-24 Thread alex23
On Sep 25, 8:32 am, Dwight Hutto dwightdhu...@gmail.com wrote: No, but phpmyadmin is a great GUI for MySQL If you're recommending MySQL use on the basis of phpmyadmin, you should also make sure to mention: http://www.phpmyadmin.net/home_page/security/ Great GUI, maybe. Huge security hole,

Re: keeping information about players around

2012-09-24 Thread Dwight Hutto
On Mon, Sep 24, 2012 at 7:28 PM, alex23 wuwe...@gmail.com wrote: On Sep 25, 8:32 am, Dwight Hutto dwightdhu...@gmail.com wrote: No, but phpmyadmin is a great GUI for MySQL If you're recommending MySQL use on the basis of phpmyadmin, you should also make sure to mention:

Re: keeping information about players around

2012-09-24 Thread alex23
On Sep 25, 9:44 am, Dwight Hutto dwightdhu...@gmail.com wrote:  What DB are you recommending, check out sqlite's: http://www.cvedetails.com/vulnerability-list/vendor_id-9237/Sqlite.html Are you _seriously_ comparing _four_ vulnerabilities to 60+? Maybe just a parsed file with data, and

Re: keeping information about players around

2012-09-24 Thread Littlefield, Tyler
On 9/24/2012 3:14 PM, Dwight Hutto wrote: I have yet another design question. In my mud, zones are basically objects that manage a collection of rooms; For example, a town would be it's own zone. It holds information like maxRooms, the list of rooms as well as some other data like player owners

Re: keeping information about players around

2012-09-24 Thread Dwight Hutto
On Mon, Sep 24, 2012 at 7:52 PM, alex23 wuwe...@gmail.com wrote: On Sep 25, 9:44 am, Dwight Hutto dwightdhu...@gmail.com wrote: What DB are you recommending, check out sqlite's: http://www.cvedetails.com/vulnerability-list/vendor_id-9237/Sqlite.html Are you _seriously_ comparing _four_

Re: keeping information about players around

2012-09-24 Thread Steven D'Aprano
On Tue, 25 Sep 2012 08:19:34 +1000, Chris Angelico wrote: On Tue, Sep 25, 2012 at 7:14 AM, Dwight Hutto dwightdhu...@gmail.com wrote: Also, If this is a browser app I'd go with phpmyadmin, and MySQL If a tkinter/wxpython/etc app, then maybe sqlite. Out of curiosity, why? MySQL isn't

keeping information about players around

2012-09-23 Thread Littlefield, Tyler
ytHello all: I've asked for a couple code reviews lately on a mud I've been working on, to kind of help me with ideas and a better design. I have yet another design question. In my mud, zones are basically objects that manage a collection of rooms; For example, a town would be it's own zone.