Prolog language for PostgreSQL proof of concept

Post by darby_eight » Sat, Mar 30, 2024, 5:13 PM UTC

qweqwe14 wrote: post #26

pjmlp wrote: post #21

Earlier quoted context omitted.

All enterprise level RDMS have similar capabilities, some of which are yet to come to Postgres.

Postgres is currently the most advanced RDMS, anyone who's not locked in by Oracle or whatever and doesn't use Postgres for new projects is likely misinformed. Postgres essentially made every other RDMS obsolete except for some niche circumstantial cases (e.g. vendor lock-in) > enterprise level Postgres is enterprise level (whatever that means). Blazingly fast, Web 3, cloud-native, etc etc, pick your own buzzwords

Post by marcosdumay » Sat, Mar 30, 2024, 5:40 PM UTC

pjmlp wrote: post #28

qweqwe14 wrote: post #26

Earlier quoted context omitted.

Postgres is currently the most advanced RDMS, anyone who's not locked in by Oracle or whatever and doesn't use Postgres for new projects is likely misinformed. Postgres essentially made every other RDMS obsolete except for some niche circumstantial cases (e.g. vendor lock-in) > enterprise level Postgres is enterprise level (whatever that means). Blazingly fast, Web 3, cloud-native, etc etc, pick your own buzzwords

The same applies to those that think Postgres does everything, every single feature, that Oracle, SQL Server, DB 2, and co, are able to deliver, in projects where their license costs are kind of irrelevant in the big context of the organization. Usually, it is a great way for many organizations to have a database as free beer.

Post by greenavocado » Sat, Mar 30, 2024, 6:02 PM UTC

ryanjshaw wrote: post #62

greenavocado wrote: post #57

Earlier quoted context omitted.

I wrote SQL queries twice that long for credit originations reports in banks which would hit several terabytes of disk read per run

Apologies, I should've been more clear. The absolute length of SQL wasn't what I was alluding to: it was the ratio of Datalog to SQL I was curious about based on this statement in the website: > Among database theoreticians Datalog and SQL are known to be equivalent. And indeed the conversion from Datalog to SQL and back is often straightforward. I was skeptical, and indeed the sample I linked to shows 8 lines of Dat…

    CREATE TABLE edges (
        source INT,
        target INT
    );

    INSERT INTO edges (source, target)
    SELECT generate_series as source, generate_series + 1 as target
    FROM generate_series(0, 999);

    WITH RECURSIVE path_lengths AS (
        -- Base case: Direct paths from edges
        SELECT source, target, 1 AS distance
        FROM edges
        UNION ALL
        -- Recursive step: Double the path length by joining on intermediate nodes
        SELECT p.source, e.target, p.distance + 1 AS distance
        FROM path_lengths AS p
        JOIN edges AS e ON p.target = e.source
        WHERE p.distance