Comments (17)
from records.
Honestly, my immediate reaction is "I'm not sure", leaning towards "no".
1. Little/No Benefit: Records, as it stands, is a very thin layer on top of psycopg2, which, for the feature set that Records currently provides, is a perfect fit. In other words, I don't think moving to something else would provide any benefit at this time.
2. Other Databases: Also, there has been some consideration for adding support for other database backends. If we were to do this, it would likely be in the form of using SQLAlchemy as a database driver. So, relying on another Postgres library would take a step away towards that (currently non–) goal.
3. Too Early: That being said, at the moment, I'm deciding to stick with Postgres-only support (mostly because of very subtle differences in the way querys can be expressed in SQLAlchemy). I'm reconsidering it constantly, though, so this is further reason to not make any big dependency commitments at this time.
from records.
Just pushed the release built on top of SQLAlchemy :D
from records.
Alright. Good luck! :-)
from records.
@whit537 😭
from records.
No worries. I think you just made DB-API 3.0, and I like it. :-)
from records.
P.S. I would be remiss not to note that @3kwa ported the basic API from Postgres.py for other databases in https://github.com/3kwa/sql.
from records.
@kennethreitz must be a better brand in the Python sphere. Thought of you @whit537 when I saw records pop all over the place.
from records.
:-)
from records.
I'm the Kanye West of Python.
(That's my Kanye impersonation)
from records.
Well, we're much less in competition now that Records is powered by SQLAlchemy. So, the sky's the limit!
from records.
Well, we're much less in competition now that Records is powered by SQLAlchemy.
Mmmm ... over here it feels like we're much less in competition because Records has already nuked Postgres.py and sql out of the water in terms of open-source mindshare.
I'm not gonna say that doesn't burn a little bit, but branding and community matter at least as much as code, and you're purty good at all three. 😸 At the end of the day what really matters is that the Python community is finally getting a sane SQL API. 🍻
from records.
^L
from records.
Wow does that mean sql is 1st in watch, star and fork 💃
from records.
Wow does that mean sql is 1st in watch, star and fork 💃
Hah! You're the best around! 💃
^L
Yeah, I finally ate crow on Aspen recently as well. Over there I never got the code to the level of polish I wanted, but I was actually really proud of Postgres.py. It was well-designed, well-documented, well-tested, ported to Python 3 ... tight!
from records.
Hey! Here's another one called Queries from @gmr. I found it on http://awesome-python.com/ after googling for "postgres python for humans."
Queries is inspired by Kenneth Reitz's awesome work on requests.
Looks like it's older than Postgres.py (initial commit on Queries is August 24, 2012, based on prior work; initial commit on Postgres.py is from Aug 7, 2013, based on internal Gittipay code going back to at least June 1, 2012).
@gmr Looks like you came in second! Or third, depending on how we're counting it. ;-)
from records.
vinta/awesome-python#567 ← Postgres.py
vinta/awesome-python#568 ← sql
vinta/awesome-python#569 ← Records
from records.
Related Issues (20)
- RecordCollection support fetch many
- records.Database.query can't return affected rowcounts? HOT 1
- mssql query works for sqlalchemy but not for records HOT 1
- (sqlite3.ProgrammingError) Cannot operate on a closed database.
- Within transaction, the error disappeared
- database connections
- Can I get multiple sql command's output
- 导出excel无异常情况,但是无法生成xls文件 HOT 1
- can not read sqlserver! data can be read using sqlalchemy but records no! HOT 2
- MSSQL Queries are broken
- Is records being maintained? HOT 3
- How to get the last sql run
- Export XLS error HOT 1
- This library may no longer be maintained, and many problems 1 year ago have not been dealt with HOT 6
- records python3 is not compatible with new sqlalchemy release 1.4.0 HOT 7
- records (v0.5.3) is incompatible with latest Pandas (v1.2.4) cause they have requires different openpyxl version dependency, is there any way to fix this issue? HOT 2
- db.query('SELECT * FROM persons) can't execute
- Records is not compatible with Python 3.8+ HOT 1
- sqlalchemy 2.0 support. HOT 1
- How to connect to oracle?Can you give me a demo?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from records.