I am using PostgRest 8.0.0 and Postgres DB v14. I am facing the following error for selection of rows in a table.
http://localhost:3000/table
error:
{
"hint": null,
"message": "invalid configuration parameter name \"request.header.user-agent\"",
"code": "42602",
"details": "Custom parameter names must be two or more simple identifiers separated by dots."
}
Edit: You should use PostgREST 9 with postgresql >= 14
PostgREST 8.0.0 is incompatible with postgres 14, see https://github.com/PostgREST/postgrest/issues/1857.
This will be fixed in a new release. For now, you can use the latest binary which contains a fix for postgres 14. You can download it here(bottom of the page).
Related
Im trying to update some values (via django) at a table on Postgres that contains a Generated column.
This is the error im getting:
column "xx_xx" can only be updated to DEFAULT
See complete error here
You cannot edit generated column in a way other columns are saved/updated
As PostgreSQL documentation states
A generated column cannot be written to directly. In INSERT or UPDATE commands, a value cannot be specified for a generated column,
but the keyword DEFAULT may be specified.
I'm setting up ColdFusion 2018 (with Update 5) and am having an issue - it seems that "Enable Null Support" option in CF Admin does nothing.
I have some API results (from a 3rd party api) that can return null values - eg; json
{
"FirstName": "Fred",
"LastName": null,
"Email": "test#test.com"
}
When I deserializeJson( theResult ) and cfdump the struct, it has "undefined" as the value for LastName. In ColdFusion 9 (which I'm porting over to CF2018), in the example given above the value for LastName shows as "null" when doing a cfdump. My issue is that in CF2018 when I try and access this variable it throws an error
Variable LastName is undefined
It doesn't seem to make a difference if you check the box for Enable Null Support in the CF Admin or not. I've tried selecting it, un-selecting it, even restarting CF after each update.
Is this a bug? I'm using CF2018 with Update 5 (version 2018.0.05.315699). Any ideas?
"Before the ColdFusion 2018 the null value from database / JSON becomes empty string. So we couldn't differentiate NULL vs EMPTY value scenario.
To provide support for null-based implementation, new version introduce null as part of language changes in ColdFusion 2018.
https://helpx.adobe.com/coldfusion/cfml-reference/coldfusion-functions/functions-c-d/DeserializeJSON.html
Since ColdFusion 10, JSON null values become undefined.
Enable Null Support in ColdFusion 2018 is different and it's nothing to do with the null values in the JSON data handling.
Only the behavior of isNull and isDefined functions will vary with the above setting.
The isNull and isDefined functions return true for a variable with null value.
Earlier, the output of isNull function is reverse of the isDefined function output, but now it checks for a variable with value null."
September update have changed how to consume data from Postgres.
M code will change to something like this:
Value.NativeQuery(PostgreSQL.Database("server", "db"), "query", null, [EnableFolding=true])
How can I change to function as before the update?
PostgreSQL.Database("server", "db", [Query="query"])
Or now I would need to do it manually?
Regards,
Finally Microsoft gave me the workarond: just remove [EnableFolding=true] from query, advance editor (the one showing the m language)
Right yesterday I went into the same issue.
Data refresh now works only from desktop while fails for any new query created with latest Power BI once published on service.
Tried to set EnableFolding=false and EnableFolding=none as error message suggests but both throwing a error.
Error while moving data from one table (nvarchar) to another table (date) within SQL Server 2014 using IICS (Informatica Cloud). I tried using expression
To_date_out = To_date(Incep_Date, 'yyyy-mm-dd')
but the same error still shows up:
TT_11019 There is an error in the port [Incep_Date]: The default value for the port is set to: ERROR(Transformation error: IUpdateStrategyNode12)
I found the answer. It seems Informatica implicitly converts the varchar in YYYY-MM-DD to YYYY/MM/DD, despite the session and the source data in a different(former) format.So in the expression, we need to convert to the latter format & it works! TO_DATE( Incep_Date, ‘YYYY-MM-DD’). Thanks #bitbangs for your time & help.
Sitecore 8.1 instance Multilist with Search field type the query included with -_name:__Standard Values does not work. However, the same query worked well in Sitecore 7.2 instance.
Here is my query:
StartSearchLocation={11111111-1111-1111-1111-111111111111}&Filter=_template:67535e3s84a5a71ab2cf8ef732819d4c|-_name:__Standard Values
When I remove this part -_name:__Standard Values, it is working fine.
Can anyone help me on how to fix this issue?
There is 1 problem as following :
You need not to have '-' after pipe and before word _name
So if you resolve this 2 error, Final string will be as follow:
StartSearchLocation={11111111-1111-1111-1111-111111111111}&Filter=_template:67535e3s84a5a71ab2cf8ef732819d4c|_name:__Standard Values