accessing postgresql

[Skaperen]

if you use postgresql from python: what is your favorite way to access postgresql in python?

i am looking to see which is more popular here.

the application i have needs to store many rows/records that each have a date range and needs to "read" all the rows/records where its range include the specified date. or could this be done just as fast with a sequential file testing each row/record to see if the date falls in the range.

[wavic]

This should be asyncpg. I've come across this recently
However, I didn't play with postgre yet. A little sqlite3

[Skaperen]

i did some PostgreSQL a few years ago when i did some web stuff for a client.  their DBA gave me the Python stuff they set up their databases with but i don't remember it and didn't save it. it was customized by them, anyway.  they were a Python shop and all their programmers used Python and R (i didn't do any of that part).  this project is one of my own and i'm not sure a relational DB will really help.

[wavic]

Pick one of the NoSQL thеn

[Larz60+]

py-postgresql: http://python.projects.pgfoundry.org/
for many things likedatabase load and create, I use psql scripts and PgAdmin which
is one of the, (if not the) best admins available.

[snippsat]

what is your favorite way to access postgresql in python?

Usually Flask-SQLAlchemy.
With this URI for PostgreSQL.

app.config['SQLALCHEMY_DATABASE_URI'] = 'postgresql://snippsat:password@localhost/app'

Sometime dataset for fast setup.
There is lot of cool stuff to use Redis, Peewee, RethinkDB, Pony ORM

[Skaperen]

yeah, i'm considering no-sql, now, or just a few plain files (with names divided up by account number modulo some chosen value).  most of the processing needs to read every record.  some will need to just read records for a specific account.

the only table relations i see is between a table of accounts (who has that account, passwords, etc) which will be small, and a table of service purchases with date-to-date of purchase, when they purchased, credit approval id, and their account.  a daily process will produce a list of accounts that purchased service for that date.  a web page will take purchases.  a web page will take support requests and insert them in a directory, including refund/cancel requests. i don't think this is so sophisticated to make a relational database an absolute necessity.

[wavic]

A document nosql database could hold all of this. I think
I didn't use one of these either.

[Skaperen]

perhaps. i have never used those, so i don't know how they structure multiple items into a record/row. but i have done that into a file in c and in python using pickle (trusted writer). i could come up with different ways if needed since i don't need to use common abstractions (just my own is good enough since it will be all my code).