6 ms·
q and kdb+ would be the better choice in my opinion. I feel as if there is better documentation, books, and resources for q than J/k
by Jorge1o1 7y ago
q and kdb+ would be the better choice in my opinion. I feel as if there is better documentation, books, and resources for q than J/k
- 7thaccount 7y agoq and k are both part of the kdb+ database software suite. K is the language and q is a DSL wrapper over k with SQL primitives. J is an entirely different language and I think the doc is actually pretty decent. There are free books and tutorials and books you can buy on Amazon.
- ithkuil 7y agoI know I can escape into the k interpreter with a \ (backslash) I don't know how to find the documentation for the k version that is shipped with kdb+ (free non commercial download). I only find broken links (it seems they removed the k documentation from kx.com website?)
- clarry 7y agoIt seems to be deliberately undocumented. This might help a bit: https://code.kx.com/q/basics/exposed-infrastructure/ https://code.kx.com/q/basics/exposed-infrastructure/ http://kparc.com/k.txt http://kparc.com/k.txt (Look up Q docs for monadic K operators by their english name)
- 7thaccount 7y agoThere is no built-in help with that interpreter? I know Shakti K has built-in help.