Support

Getting help

Most questions are answered by one of the two manuals. The language reference has a page per operator, predicate and function, each with a worked example; if you know the glyph but not the name, find an operator resolves every spelling — glyph, keyword and stem — to its page. The programming guide covers the Java side: opening a session, getting data in, building and running a query, and reading back what the engine decided.

When a query does something you did not expect, the engine will tell you why it did it, and from your own program rather than from a log. A relation renders its physical plan and the SQL it pushed to the source, reports which rewrites the optimiser applied, and publishes the feed of decisions behind both. Seeing what the engine decided covers all three. Between them they usually answer the question faster than asking someone would.

Reporting a problem

Bugs and feature requests go to the issue tracker, which offers a template for each. A good bug report is the smallest script that shows the behaviour, what you expected it to do, what it did instead, and the rows of relix.version — that relation names the engine, the Java it is running on and every component the run actually found, which is the difference between a missing provider and a wrong answer. If the script reads a database, the schema of the tables it touches matters as much as the query.

Reports about the manuals are as welcome as reports about the engine. Their examples are checked on every build — the guide's Java is compiled and run against the printed output, the reference's queries are analysed, and its worked examples are executed and diffed against the rows shown beside them — so a page that does not behave as it reads is a defect in the same sense a wrong answer is.

Supporting Relix

Relix is Apache-licensed and free to use, and that does not change. If it has saved you time and you would like to put something back, there are three ways to do it: GitHub Sponsors, Ko-fi, or Buy Me a Coffee.

None of them buys support or priority. Issues are read in the order they arrive whether or not the person reporting one has sponsored anything, and no part of the engine is held back for sponsors — what the money buys is time spent on the project rather than on something else.