OctoSQL is definitely not in a stable state yet, so depending on the use case, there definitely are rough edges and occasional regressions.
> Missing FULL JOIN (this was a dealbreaker for me). LEFT/RIGHT join gave me "panic: implement me".
Indeed, right now only inner join is implemented. The others should be available soon.
> replace() is documented [1] as replace(old, new, text) but actually is replace(text, old, new) just like in postgres and mysql.
index() is documented [1] as index(substring, text)
I've removed the offending docs pages, they were documenting a very old version of OctoSQL. The way to browse the available functions right now is built-in to OctoSQL:
octosql "SELECT * FROM docs.functions"
> invalid argument syntax error at position 13 near 'index'
Looks like a parser issue which I can indeed replicate, will look into it.
Just to update this response, I've just released a new version that contains a new `position` function, as well as the capability to execute SELECT statements without a FROM part. So i.e. the above
Thanks a lot for this writeup!
> but I immediately ran into many rough edges
OctoSQL is definitely not in a stable state yet, so depending on the use case, there definitely are rough edges and occasional regressions.
> Missing FULL JOIN (this was a dealbreaker for me). LEFT/RIGHT join gave me "panic: implement me".
Indeed, right now only inner join is implemented. The others should be available soon.
> replace() is documented [1] as replace(old, new, text) but actually is replace(text, old, new) just like in postgres and mysql. index() is documented [1] as index(substring, text)
I've removed the offending docs pages, they were documenting a very old version of OctoSQL. The way to browse the available functions right now is built-in to OctoSQL:
> invalid argument syntax error at position 13 near 'index'Looks like a parser issue which I can indeed replicate, will look into it.
Thanks again, cheers!