dual | New icon theme for Linux with dualtone | Theme library

If there's only one row of data, then you can use

As mentioned in the docs:

For SQL statements where a colon is required verbatim, as within an inline string, use a backslash to escape

But remember that the backslash is also the escape character in Python string literals, so

The solution was to change imx7d-pico-pi-m4.dtb to imx7d-pico-pi-qca-m4.dtb in the Yocto/Hardknott/technexion configuration file called pico-imx7.conf(described in the post)

This particular query seems to be an attempt to implement string split(Related: Splitting string into multiple rows in Oracle):

Though very late, I'll try to give my answer. According to the doc, here's the considered primal optimization problem for LinearSVC: ,phi being the Identity matrix, given that LinearSVC only solves linear problems.

Effectively, this is just one of the possible problems that LinearSVC admits (it is the L2-regularized, L1-loss in the terms of the LIBLINEAR paper) and not the default one (which is the L2-regularized, L2-loss). The LIBLINEAR paper gives a more general formulation for what concerns what's referred to as loss in Chapter 2, then it further elaborates also on what's referred to as penalty within the Appendix (A2+A4).

Basically, it states that LIBLINEAR is meant to solve the following unconstrained optimization pb with different loss functions xi(w;x,y) (which are hinge and squared_hinge); the default setting of the model in LIBLINEAR does not consider the bias term, that's why you won't see any reference to b from now on (there are many posts on SO on this).

• , hinge or L1-loss
• , squared_hinge or L2-loss.

For what concerns the penalty, basically this represents the norm of the vector w used. The appendix elaborates on the different problems:

• L2-regularized, L1-loss (penalty='l2', loss='hinge'):
• L2-regularized, L2-loss (penalty='l2', loss='squared_hinge'), default in LinearSVC:
• L1-regularized, L2-loss (penalty='l1', loss='squared_hinge'):

Instead, as stated within the documentation, LinearSVC does not support the combination of penalty='l1' and loss='hinge'. As far as I see the paper does not specify why, but I found a possible answer here (within the answer by Arun Iyer).

Eventually, effectively the combination of penalty='l2', loss='hinge', dual=False is not supported as specified in here (it is just not implemented in LIBLINEAR) or here; not sure whether that's the case, but within the LIBLINEAR paper from Appendix B onwards it is specified the optimization pb that's solved (which in the case of L2-regularized, L1-loss seems to be the dual).

For a theoretical discussion on SVC pbs in general, I found that chapter really useful; it shows how the minimization of the norm of w relates to the idea of the maximum-margin.

Is there a way to use an inline function in subquery (in a WHERE clause)?

There is, but I am not sure if this will help you. I don't know what a COTS system is, and how it works. I understand that users can only enter a WHERE clause; but do you (as a developer) - or whoever the developer is, if it's not you - have access to the entire SELECT statement?

If the query in which you define a function in the WITH clause is not the top-level SELECT statement (in your case it isn't), then the top-level SELECT must include the with_plsql hint. (Oracle calls it a "hint", anyway; it uses the hint syntax, but it's not a hint, it is really a compiler directive.) Alas, this must be in the top-level SELECT (meaning the SELECT clause of your query, which is not accessible by your end user).

This is why I asked... if whoever develops these queries for your users doesn't mind adding the with_plsql hint to the top-level SELECT, then you can do what you asked. The hint won't hurt anything if a user types a WHERE clause with no PL/SQL code in a WITH clause, so there should be no reason not to want to do this; but, like I said, I don't know what COTS means or how it works.

To get a cookie from an AJAX request within APEX, you can use the OWA_COOKIE package, but you do not need to define any templates or handlers. It can all be done from within the page (or calling an external procedure from within the page). Below are the steps I used to get the JSESSIONID cookie.

I have built an example application on apex.oracle.com that you can check out.

The page is very simple with just one text box and one button. The button's action is set to Redirect to URL and this is the target:

sqlplus inherits the code page/encoding from parent cmd window. NLS_LANG tells the database which characterset/encoding is used by the client. So, when you run