Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #29942 > unrolled thread

Re: keeping information about players around

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: keeping information about players around Chris Angelico <rosuav@gmail.com> - 2012-09-25 08:19 +1000
    Re: keeping information about players around Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-09-25 02:29 +0000

#29942 — Re: keeping information about players around

On Tue, Sep 25, 2012 at 7:14 AM, Dwight Hutto <dwightdhutto@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 web browser. Unless you're planning
to also reference this database from some other language, it's going
to make little difference what backend you use; and even if you are
using multiple languages, it's usually not difficult to find overlap.

ChrisA

[toc] | [next] | [standalone]

#29998

On Tue, 25 Sep 2012 08:19:34 +1000, Chris Angelico wrote:

> On Tue, Sep 25, 2012 at 7:14 AM, Dwight Hutto <dwightdhutto@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 web browser. Unless you're planning to also
> reference this database from some other language, it's going to make
> little difference what backend you use; and even if you are using
> multiple languages, it's usually not difficult to find overlap.

For a desktop application, you can't expect the application user to have 
set up MySQL or Postgresql first, so you have to use something like 
sqlite.

For web applications, you're probably expecting (or at least hoping for) 
tens of thousands of users a day, and sqlite probably won't cut it. If 
your web app is only used by you, then you might not care.

I think it is perfectly reasonable to assume a web app and a desktop app 
might use different backends.



-- 
Steven

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web