(1) You can find more at Kayia.org but more will be posted on the site soon.
(2) A nontrivial application example is not available just yet and I agree with you that it would a great place to examine its trade-offs. The next several months will be quite busy but if you could please check in after that and I think we can eventually get you an answer you'll be quite pleased with.
So, which is it: do I begin with a schema or not? If I don't need to think about the cardinality of relationships, then I don't have a schema. (My definition of “schema” is “a DBMS-enforced description of the logical structure of a database”. If I don't have to think about it, how can the DBMS enforce it?)
> You can find more at Kayia.org
The syntax is properly specified, but the semantics is not. Also, I keep getting lots of JavaScript errors when I try to use your website.
Let's say now you find out that one film has two directors (a change in relationship cardinality). If you have not constrained it, the default is to allow that to happen.
You have schema. The default, though, is to let the data tell you what it is rather than the other way around.
> Kayia.org The syntax is properly specified, but the semantics is not. Also, I keep getting lots of JavaScript errors when I try to use your website.
There's also a lot of missing information. My apologies; fixes are coming. We didn't plan to submit this to Apply HN -- the opportunity just jumped and so did we. We should have waited and fixed those things and then submitted. Again, apologies, changes are coming.
(1) Could you provide a proper specification of Brodlist's query language? Your example is too small to convince me that Brodilist's query language can express everything SQL can express.
(2) Could you provide an example of a nontrivial application (like a small ERP module) that illustrates how Brodlist is more convenient to use than a traditional SQL DBMS?