Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
value too long for type character varying(256)
See original GitHub issueSaving CI project test-lhci-7068 (d64e99f0-15fd-466a-88b2-9a07f20ac1b9)
Saving CI build (aa5702e1-30b7-4811-b392-b45cd34a5989)
Error: Unexpected status code 422
{"message":"value too long for type character varying(256)"}
at ApiClient._convertFetchResponseToReturnValue (/usr/local/lib/node_modules/@lhci/cli/node_modules/@lhci/utils/src/api-client.js:55:21)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
Strange PostgreSQL "value too long for type character varying ...
In the documentation for Postgres it says type text can have unlimited characters. I'm using postgresql-9.1. This table has been generated using ...
Read more >How do I correct this value too long for type character varying ...
So first, what's the difference.. SELECT x, length(x) FROM ( VALUES ('Cincinnati'), ('San Francisco') ) AS t(x);. Here is the output
Read more >U112: Value too long for type - pganalyze
This error indicates that you were passing data to a column that is too large to be held by its data type, usually...
Read more >What Do I Do If the Error Message "value too long for type ...
The length of the varchar field of DWS is calculated by byte, and a Chinese character may occupy three bytes in UTF-8 encoding....
Read more >ERROR: value too long for type character varying(256)
PSQLException: ERROR: value too long for type character varying(256) , NULL, NULL) was aborted. Call getNextException to see the cause.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for filing @lili21! We’re going to have to put some limit on the URL for performant queries, so the questions are:
Right now the answers are
Alternatives:
Any preferences here?
I’d prefer the 3rd alternative - only save the first X characters of the URL. and mentioned this in the docs.