3 ms·
first off, thanks for the links. Secondly, > That doesn't really change the equation. You still either have to (1) choose your DBMS's query language to write y
by ZenPsycho 8y ago
first off, thanks for the links. Secondly,
> That doesn't really change the equation. You still either have to (1) choose your DBMS's query language to write your application server (like today) or (2) use one language to construct queries in another (like today).
I don't know if you're misunderstanding me, or I'm misunderstanding you. prolog is a query language. The logical programming paradigm is that a program is a "list of facts" and you run the program by "querying" the state of the world. The only piece missing is making the fact storage engine scalable/robust/production ready. Or.. alternatively, there's the Eve[1] project which starts off with prolog to make a hypercard like environment with a built in data storage layer. Its aim is less production ready apps and more developer ergonomics.
[1]: ( http://witheve.com http://witheve.com )
- paulddraper 8y agoI don't think I misunderstood. You yearn for the day when a DBMS uses Prolog for its query language. Users of that DBMS have the choice to either (1) query seamlessly because they use prolog for the entire application (2) query by "gluing" Prolog to their application language.