Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Can pandas be used as a database backend for persistent storage?

Parent

Can pandas be used as a database backend for persistent storage?

+2
−1

Question

What is the current state of the art database app? How does it compare to SQL? Can pandas be used in place of either?

If not, is there something that bridges the gap between SQL and pandas or the current state of the art?

Context

I have become proficient in pandas and have come to like the syntax. I have experience with SQL, but would have to study my notes to get back up to speed, and find the syntax rather tedious.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+1
−0

SQL is as good as it gets, generally speaking. The best engine for a small project is SQLite. If you need more, the next step is Postgres. Postgres is very capable and it's unlikely that you'll need more even as a medium sized company. But it sounds like you're asking about small personal projects.

"State of the art" that goes beyond SQL/Postgres is usually about scalability and division of labor. These are concerns relevant to large companies (Facebook, Netflix, ...) and not for personal projects. By using these cutting edge DBs, you will be accepting compromises that make your life more difficult, and gaining benefits that don't apply to you.

As stated elsewhere, you can read/write from a SQL DB with Pandas, and many DB connectors support some kind of .to_pandas method. However, this won't save you form learning SQL, since you'll still have to pass the queries to fetch and upsert the data. Pandas also has a looser typing system than the typical DB, so you might often run into annoying type mismatch/conversion bugs there.

Instead of a DB, you can use pandas to read/write some simple file format, like CSV or Parquet. I would recommend CSV, it's easy to work with using other tools as well. If you want something nested, then JSON is a good start.

You should really just learn SQL. Pandas at its heart is a crude reimplementation of things SQL has perfected half a century ago.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

MySQL (1 comment)
MySQL
manassehkatz‭ wrote over 1 year ago

SQLite has its place - no separate process running. And PostgreSQL is fine too. But for a lot of projects, from small dedicated systems on up to mirrored servers in the cloud, MySQL works just fine. In certain ways it is simpler than PostgreSQL, but it is quite powerful and scalable, and just about every language that supports PostgreSQL also supports MySQL (and mostly vice versa). There are also some tools (particularly phpMyAdmin) for MySQL that are, in some ways, more user-friendly than the equivalent in PostgreSQL. If you like PostgreSQL, use it (I do). If you like MySQL use it (I do, more than PostgreSQL). When you look at the basics (free, scalable, compatible with many languages) they're very, very similar.