Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrading from 2.0.3 to 2.0.4 postgis errors #800

Open
paolantoni opened this issue Jul 23, 2019 · 1 comment
Open

upgrading from 2.0.3 to 2.0.4 postgis errors #800

paolantoni opened this issue Jul 23, 2019 · 1 comment

Comments

@paolantoni
Copy link

upgrade causes the delete of two scripts in app-host server:
/opt/web/dist/scripts/scritps.js
/opt/schema_editor/dist/scripts/scripts.js
because of parsing error .

After forcing the build and replacing manually the scripts there is an error with postgis:
/api/records/costs/?archived=False&details_only=True&occurred_max=2019-07-23T20:24:17.144Z&occurred_min=2019-04-24T20:24:17.144Z&record_type=4a56c78f-4348-4832-aba8-be8d536d78be

{record_type: "No cost configuration found for this record type."}
record_type: "No cost configuration found for this record type."

and also:

GET /api/records/costs/?archived=False&details_only=True&occurred_max=2019-07-23T20:24:17.144Z&occurred_min=2019-04-24T20:24:17.144Z&record_type=4a56c78f-4348-4832-aba8-be8d536d78be

"detail": "Authentication credentials were not provided."

what's happening?
The application is not showing layers on maps but the db password have never been changed.

@paolantoni
Copy link
Author

further details:
{"error":"Postgis Plugin: ERROR: syntax error at or near "::"\nLINE 1: ...l"::varchar, U0."username") AS "email_or_username"::varchar ...\n ^\n\nin executeQuery Full sql was: 'SELECT * FROM (SELECT "grout_record"."uuid"::varchar, "grout_record"."created"::varchar, "grout_record"."modified"::varchar, "grout_record"."schema_id"::varchar, "grout_record"."data"::varchar, "grout_record"."archived"::varchar, "grout_record"."occurred_from"::varchar, "grout_record"."occurred_to"::varchar, "grout_record"."geom", "grout_record"."location_text"::varchar, "data_driverrecord"."record_ptr_id"::varchar, "data_driverrecord"."weather"::varchar, "data_driverrecord"."light"::varchar, "data_driverrecord"."city"::varchar, "data_driverrecord"."city_district"::varchar, "data_driverrecord"."county"::varchar, "data_driverrecord"."neighborhood"::varchar, "data_driverrecord"."road"::varchar, "data_driverrecord"."state"::varchar, (SELECT COALESCE(U2."email"::varchar, U0."username") AS "email_or_username"::varchar FROM "data_recordauditlogentry" U0 LEFT OUTER JOIN "auth_user" U2 ON (U0."user_id" = U2."id") WHERE (U0."action" = 'create' AND U0."record_id" = ("data_driverrecord"."record_ptr_id")) LIMIT 1) AS "created_by" FROM "data_driverrecord" INNER JOIN "grout_record" ON ("data_driverrecord"."record_ptr_id" = "grout_record"."uuid") INNER JOIN "grout_recordschema" ON ("grout_record"."schema_id" = "grout_recordschema"."uuid") WHERE ("grout_recordschema"."record_type_id" = '4a56c78f-4348-4832-aba8-be8d536d78be'::uuid AND "grout_record"."occurred_to" >= '2019-07-09T21:00:11.602000+00:00'::timestamptz AND "grout_record"."archived" = false) ORDER BY "grout_record"."occurred_from" DESC) as grout_record LIMIT 0'\n encountered during parsing of layer 'grout_record' in Layer"}

Could you please give support?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant