alps | predictive modeling background worker for postgres | Machine Learning library

ALPS descriptions don't make distinctions between single items and collections. From the model POV anything could be a collection, from the implementation POV, each service implementing that ALPS description makes their own decisions.

as a common practice, i typically use the IANA link-rel values when it is important

If you want to set a maximum of visible elements in the QCompleter then you must use the maxVisibleItems property:

It is possible to bundle everything on one war, but I see it more convenient not to put different applications (backend war and frontend dist content) mixed together as one mess, where we both already are looking which part responds and where.

Easier, far more easier actually, is to apply the following config:

I formatted your code so it's readable. And by indenting it, you can see where the problem is. It's in line 6/7 in the "FROM" part. Oracle can't really figure out what you're trying to do with that statement and when the parser reaches the end of the query at "(+)", he tells you that there is something missing/awkward. That's why he tells you it's the "(+)". But the problem is earlier. It's the way your build your "FROM" part. It's a bit confusing, so here is just a pointers:

when using "union", you don't give an alias to each of the two queries. The result set of both queries is "unioned", so you can't reference either of them in the "WHERE" part.

You should rewrite your query and instead of joining Client with a Union, you should Union two separate queries: one joining Client with casual_jobs, one joining Client with contrac_job. Following example is done without testing it in an SQL tool:

You need to register bean for showing h2 console like:

You should try to set the following property spring.datasource.platform to mysql. Thus, Spring Boot will be able to load the data-${platform}.sql file.

You can find more details here.

Your og implementation only works on some versions of whats app. And that is because the url (of the entire page, not just the image) contains non ascii characters.

I have copy/paste your html code on one of my web-sites and it worked ok, as long as the file was named index.html or ogtest.html.

After I renamed the file with Greek characters, og-protocol stopped working.

I think the error is caused by the redundant ,

It's not possible to check the contents of a field if you don't know its name. There are no wildcards or iterators in security rules that let you discover random things.

If you must keep this document structure and validation logic, consider instead sending the document data to a backend you control, and use server-side logic to determine if the data is valid.