-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: PumpkinDB is too low-level #325
Comments
I am working on the first prototype of ViewDB, here's an excerpt from its README: ViewDBViewDB is a database that allows inferring multiple, potentially overlapping At its heart, it is not too dissimilar from the concept of event sourcing, Facts (this name was chosen instead of "events" to further clarify their I've got some interesting ideas as to how everything can be simplified down to attributes and how this can lead to fluid yet explicit fact schemas. |
The biggest issue here is IMO that projecting 'facts' to entities/models/whatever requires a lot of business logic. So you need a (ideally strongly typed) language to define that business logic. Any ideas on that front? |
Yes, there has been a plan to introduce Typed PumpkinScript. Essentially a type checker for PumpkinScript. Just haven't got around to do that. |
Here's the issue on that: #141 |
But PumpkinScript is way too low level for normal devs to write business logic in. |
That is also very true. There were some conversations about building either transpilers for other "higher level" languages into [Typed] PumpkinScript and/or compiling to a common intermediate representation, which is yet to be done, but very necessary anyway. |
I just published an overview of ViewDB's core ideas: https://github.com/ViewDB/ViewDB#readme |
i dont mind its low level. but i do mind of its lack of examples |
For most end-user cases, PumpkinDB is too "close to the metal" to be easily plugged into a business application, especially if "event sourcing" type of scenarios are considered.
Proposed solution: implement a higher level database on top of PumpkinDB
The text was updated successfully, but these errors were encountered: