I did some something like this a while ago:
Prolog language for PostgreSQL proof of concept
41–50 of 83 posts
Re: Prolog language for PostgreSQL proof of concept
#42Earlier quoted context omitted.
There’s one thing Postgres doesn’t provide. It doesn’t provide a supplier who a company can put their liability on. A supplier who can fix the problem in Postgres code and maintain it with authority. But don’t get me wrong. Postgres is an awesome database system.
What does 'put their liability on' mean to you? Because I suspect it does not mean what I think you think it means. (Typically the EULA of all those non-Postgres systems are 'this is sold as is, no warranty as to suitability to your purpose, yada yada' Often times people believe that if they're paying many monies for a support contract, that means they can relocate their liability to that company. Almost every time,…
the product is sold as such but there are support contracts to cover everything else
Re: Prolog language for PostgreSQL proof of concept
#43Postgres is not just a relational db. It's a way of life. JSONB, HSTORE, LTREE, Full Text Search, Logical Replication, Range Types, BRIN Indexes, GIN Indexes, GiST Indexes, SP-GiST Indexes, Table Inheritance, Foreign Data Wrappers, XML Support, UUID-OSSP, pg_trgm, Cube, Earthdistance, pg_prolog, pg_partman, pgvector, TimescaleDB, PostGIS, Citus, pg_cron, BDR (Bi-Directional Replication), PL/Python, PL/Java, PL/V8, pg…
All enterprise level RDMS have similar capabilities, some of which are yet to come to Postgres.
Postgres is an open-source platform with a thriving ecosystem. People have written a vector plugin to follow the AI boom, and will likely have whatever people have an interest for.
Re: Prolog language for PostgreSQL proof of concept
#44Earlier quoted context omitted.
There’s one thing Postgres doesn’t provide. It doesn’t provide a supplier who a company can put their liability on. A supplier who can fix the problem in Postgres code and maintain it with authority. But don’t get me wrong. Postgres is an awesome database system.
i beg to differ: Professional Services https://www.postgresql.org/support/professional_support/
Most of these are consultants specialising in hosting and “consulting”. There’s even AWS in there. How much does it cost to be on that list?
Re: Prolog language for PostgreSQL proof of concept
#45Earlier quoted context omitted.
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.
Sure, a few organizations may actually need some obscure feature that Oracle provides, but again, it's niche. For most companies, Postgres provides way more features than they will ever use. And for the other 1%, it sometimes happens that their need for a specific feature in Oracle DB turns out to be entirely unnecessary. Not to mention that the vast majority of products turn out to be fancy CRUD apps. Doesn't matter…
I’d argue that, the real value of Postgres isn’t that it has capabilities on par with Oracle, but rather that, it has a thriving plugin ecosystem. If someone needs that obscure Oracle feature, they may have the option of writing it. If there’s something a lot of people are interested in (such as vector features), someone will implement it.
Re: Prolog language for PostgreSQL proof of concept
#46If you're interested in this I would also recommend you check out Logica[0], which is a datalog-like language that is explicitly made to compile to SQL queries. 0: https://logica.dev/
I was wondering how this was possible and then found this monstrosity: https://colab.research.google.com/github/EvgSkv/logica/blob/...
Click on the SQL tab.
Re: Prolog language for PostgreSQL proof of concept
#47Re: Prolog language for PostgreSQL proof of concept
#48Earlier quoted context omitted.
If your entire database can be lifted into the application's heap, it's probably small enough that I wonder why you've got it stored in an RDBMS... and because Prolog is lexically sensitive (order of sentences and the order of clauses in the sentence affect the eval result) then you would need to effectively load all related DB entries -- or maybe some cursor tricks to load domain entries lazily and the many small qu…
> If your entire database can be lifted into the application's heap, it's probably small enough that I wonder why you've got it stored in an RDBMS I think he meant lifting the database schema, not the whole database. This would help with auto completion and other static checks before trying to run queries.
Much much more important would be the foreign keys. If I remember my prolog correctly, this:
parent(alice,bob).
Re: Prolog language for PostgreSQL proof of concept
#49Earlier 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
> Postgres is enterprise level (whatever that means). Blazingly fast, Web 3, cloud-native, etc etc, pick your own buzzwords
it has issues in several choke points: HA setup is complicated, it doesn't utilize multi-core machines well on heavy queries.
Re: Prolog language for PostgreSQL proof of concept
#50Earlier 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
> enterprise level (whatever that means)
It means "non-technical executives/managers recognize the name and will approve its use". Like Oracle.