kevinsullivan - Hey folks, it's kind of unclear...
Hey folks, it's kind of unclear from quick search results whether lists, structs, etc., are yet available? I'm assuming no, though the GPTs say yes. Is it no? If so, any ETA?
10 Replies
@kevinsullivan we've deferred both of those for a while to push on other things - structs are closer and require less dramatic work, but are also pushed back until we see clear customer signals for!
Thank you for that. In the meantime, is there an idiomatic, all purpose solution to store and retrieve polymorphic list values (included lists of lists, etc.) in TypeDB3? Fine that it's not built in, but seems like this would be an expected, maybe common, use case.
Last question, not to test your patience, and thank you: is there an up to date precise complete and ideally formal and machine type-checked definition of the tyoe theory of TypeDB? We know of the paper and ACM SIGPLAN award -- that was great, congrats!
Hi again! Unfortunately, lists are still not implemented in TypeDB 3. The planned behavior is described in the roadmap: https://typedb.com/blog/typedb-3-roadmap#lists-for-data-series-and-serialized-results-4
If I understand the question correctly, it's exactly what you're looking for as a built-in solution. We currently process a number of enquiries regarding important features extending TypeDB 2's capabilities, and have not yet been able to complete this massive feature.
I'm not sure if it's something suitable for your case, but we have an ongoing conversation regarding typed lists in a parallel thread here. Maybe you can find some inspiration for solutions with the current feature stack:
https://discord.com/channels/665254494820368395/699946888572567611/1413211154020565002
TypeDB 3.0 Roadmap
The upcoming release of version 3.0 will represent a major milestone for TypeDB: it will bring about fundamental improvements to the architecture and feel, and incorporate pivotal insights from our user-base and research.
I'm looking for an idiomatic way to store and retrieve values of polymorphic list types pending release of a built-in feature. We're having trouble with a fetch query that works in all cases.
Can you share the problematic query and your current schema?
I'll get with my PhD student, Nick, later today and we'll respond together then. At some point we'll be able to share details on the larger project. You all might find aspects of it interesting. Also, is there an up-to-date formal specification of the type theory of TDB? We know about the ACM paper. Thank you very much!
Sure, please come back when you're ready! We're here to assist.
The latest, not currently maintained, very formal specification is located here https://github.com/typedb/typedb/blob/master/docs/archived/spec_old.md
We transitioned to a more practical blueprints approach (they are located in the parent directories) for better maintenance by the engineering team, but the page referenced above is not far from the current state, excluding the unimplemented things (mostly lists).
ps @georgii proprietary is normally referring to something private or intellectual property-like -- our blueprints are just a simpler format to hold the specifications, but still public in our typedb repo 🙂
Thanks. Anything machine readable/checkable, e.g., in Lean4 or Rocq?
no unfortunately not @kevinsullivan - would love if someone wanted to write that up though 😉
are you guys researchers?