HN user

assface

794 karma
Posts4
Comments88
View on HN

This list is useless. What are the salient aspects of Python programs versus other programming langs/environments (e.g., Javascript, C++) that imposes different demands on a database system?

The answer is 'nothing'. So just use Postgres.

I'm wondering if it would be worth skipping the SQL layer and compiling straight to the execution plan level.

You have to join five tables in a query. What join order will you pick in your execution plan? Will you use the same ordering for different WHERE clause parameters? What if you add an index?

What you're proposing was tried in the 1970s (see CODASYL) and it was a terrible idea.

PostgreSQL 14 5 years ago

maybe zheap will help?

According to Robert Haas, the zheap project is dead.

EdgeDB: EdgeQL 5 years ago

that aims to surpass SQL in querying power.

What makes your approach likely to succeed versus all previous attempts to supplant SQL in the last 40 years?

The second one (mid 2000s) was a neat physical storage trick, which should have been a feature of a database system, not an excuse for building a new one.

Can you say what database this was? Akiban? SchoonerSQL?

AFAIK It uses the MySQL frontend with a heavily modified InnoDB engine that writes to their shared-disk storage.