Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #56256
| References | <l2pois$359$1@dont-email.me> <l2ppnh$9fc$1@dont-email.me> <l2puok$5i8$1@dont-email.me> <l2qvju$hoi$1@dont-email.me> <CAMw+j7L+M8-qWL4yyihfqGcqzNA7_=BMQx3ExrH9zds8apg=bg@mail.gmail.com> |
|---|---|
| Date | 2013-10-07 00:37 +1100 |
| Subject | Re: Database engine bindings for Python (was: Database statements via python but database left intact) |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.781.1381066683.18130.python-list@python.org> (permalink) |
On Sun, Oct 6, 2013 at 8:10 PM, Chris “Kwpolska” Warrick <kwpolska@gmail.com> wrote: > It would require Postgres around people’s (or at least packagers’) > systems, and it often gets messy when we have such requirements. I would hope that an absence of libpq could simply result in a courteous exception when the module's imported, but maybe that'd be hard to implement. > Also, Postgres is much harder to configure than MySQL, > especially if you have no experience or an asshole OS. You can get a ready-to-go Postgres under Debian by simply apt-getting it. The default config might not give you optimum performance, but it'll work just fine. Most people shouldn't need to dig into the configs of _any_ database before getting the app going - out-of-the-box settings should be fine for early development, even deployment if you're not doing a lot of traffic. > Moreover, the stdlib is where packages come to die. Fair point. That is an issue. > We should also educate people on how PostgreSQL works with a nice, > human-friendly tutorial. Especially in some non-standard things and > things that differ between PostgreSQL and MySQL — like how to make an > auto-incrementing ID field (use sequences), or how PostgreSQL arrays > work, among others. The wiki (that nobody reads anyways) could also > use some marketing fixes. Maybe! Possibly go a bit further and say "How-to: Python and Databasing", which could mention SQLite (great for something tiny), PostgreSQL (great for concurrency / multi-user), and "Other databases can also be used, with similar or identical APIs - check out PyPI for a module for your favorite database engine". I guess the above paragraph is sentencing [1] me to write the article, now... ChrisA [1] if you'll pardon a terrible pun
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Database statements via python but database left intact Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-10-05 22:16 +0300
Re: Database statements via python but database left intact Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-10-05 22:27 +0300
Re: Database statements via python but database left intact Zero Piraeus <z@etiol.net> - 2013-10-05 16:29 -0300
Re: Database statements via python but database left intact Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-10-05 22:36 +0300
Re: Database statements via python but database left intact Ian Kelly <ian.g.kelly@gmail.com> - 2013-10-05 14:31 -0600
Re: Database statements via python but database left intact Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-10-06 00:02 +0300
Re: Database statements via python but database left intact Ned Batchelder <ned@nedbatchelder.com> - 2013-10-05 17:39 -0400
Re: Database statements via python but database left intact Chris Angelico <rosuav@gmail.com> - 2013-10-06 09:51 +1100
Database engine bindings for Python (was: Database statements via python but database left intact) Ben Finney <ben+python@benfinney.id.au> - 2013-10-06 12:05 +1100
Re: Database engine bindings for Python (was: Database statements via python but database left intact) Chris Angelico <rosuav@gmail.com> - 2013-10-06 12:19 +1100
Re: Database engine bindings for Python (was: Database statements via python but database left intact) Dan Sommers <dan@tombstonezero.net> - 2013-10-06 06:22 +0000
Re: Database engine bindings for Python (was: Database statements via python but database left intact) Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-10-06 11:10 +0200
Re: Database engine bindings for Python (was: Database statements via python but database left intact) Chris Angelico <rosuav@gmail.com> - 2013-10-07 00:37 +1100
Re: Database engine bindings for Python (was: Database statements via python but database left intact) Roy Smith <roy@panix.com> - 2013-10-06 10:05 -0400
Re: Database statements via python but database left intact Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-10-06 11:05 +0200
Re: Database statements via python but database left intact rusi <rustompmody@gmail.com> - 2013-10-06 04:36 -0700
Re: Database statements via python but database left intact Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-10-06 14:01 +0200
Re: Database statements via python but database left intact Zero Piraeus <z@etiol.net> - 2013-10-05 18:45 -0300
Re: Database statements via python but database left intact Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-10-06 18:57 +0300
Re: Database statements via python but database left intact Piet van Oostrum <piet@vanoostrum.org> - 2013-10-06 17:40 -0400
Re: Database statements via python but database left intact Adam Tauno Williams <awilliam@whitemice.org> - 2013-10-06 11:55 -0400
Re: Database statements via python but database left intact Adam Tauno Williams <awilliam@whitemice.org> - 2013-10-06 11:52 -0400
Re: Database statements via python but database left intact Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-10-06 19:49 +0300
csiph-web