Sandro Santilli
Sandro Santilli
also note as the VARCHAR return was moved below the RETURNS line, before the `WITH (NOT VARIANT)` statement which is also bogus (see #21)
The problem only occurs with `RETURNS`. Changing the statement to `RETURNING` fixes it.
#26 fixes this case by using the existing `ParseInformixReturns` for both `RETURNS` and `RETURNING`
Ok I think `WITH (NOT VARIANT)` needs to be translated to `IMMUTABLE` as a parameter of PostgreSQL function.
Pull request #24 deals with this problem, fixing it for the specific case (can probably be generalized further)
We are using LDAP as authentication backend which I believe only creates a local user record on first login. This means the name of a legit user will not be...
See also https://github.com/go-gitea/website/issues/70
> @sapk Awesome! Did you just query the api of the instances and then put it in elasticsearch? Query the API of _which_ instances ? How did you find instances...
I'm annoyed by the contrary on the Android version: you cannot tell it's a watchonly, it doesn't even hide the "send" button
I figured about the transaction preparation but then maybe the "Send" button text should be replace with a "Prepare transaction" text or something