Strange Postgresql "Value Too Long for Type Character Varying(500)"

Strange PostgreSQL value too long for type character varying(500)

By specifying the column as VARCHAR(500) you've set an explicit 500 character limit. You might not have done this yourself explicitly, but Django has done it for you somewhere. Telling you where is hard when you haven't shown your model, the full error text, or the query that produced the error.

If you don't want one, use an unqualified VARCHAR, or use the TEXT type.

varchar and text are limited in length only by the system limits on column size - about 1GB - and by your memory. However, adding a length-qualifier to varchar sets a smaller limit manually. All of the following are largely equivalent:

column_name VARCHAR(500)

column_name VARCHAR CHECK (length(column_name) <= 500) 

column_name TEXT CHECK (length(column_name) <= 500) 

The only differences are in how database metadata is reported and which SQLSTATE is raised when the constraint is violated.

The length constraint is not generally obeyed in prepared statement parameters, function calls, etc, as shown:

regress=> \x
Expanded display is on.
regress=> PREPARE t2(varchar(500)) AS SELECT $1;
PREPARE
regress=> EXECUTE t2( repeat('x',601) );
-[ RECORD 1 ]-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
?column? | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and in explicit casts it result in truncation:

regress=> SELECT repeat('x',501)::varchar(1);
-[ RECORD 1 ]
repeat | x

so I think you are using a VARCHAR(500) column, and you're looking at the wrong table or wrong instance of the database.

org.postgresql.util.PSQLException: ERROR: value too long for type character varying(255)

You try to save a string value more than 255 chars length. Just increase a column length

@Column(name = "xxx", length = 1024)

you need to alter a column length in the database too.

When you use

@Column(name = "xxx")

Hibernate uses a default column length.

You can use @Lob for a really large text data.

Please, use xxx_users in place of tblusers.

Use User in place of Users.

Use CascadeType.ALL on the @OneToMany part of the association.

Use a lazy loading on the @ManyToOne part of the association.

@ManyToOne(fetch = FetchType.Lazy)
pravate User user;

value too long for type character varying(25)

i 've found the problem:
I checked the upload with multiple csv files and saw that the error always occured when the assetclass field contained the string Sonstige Vermögensgegenstände . So I commented out the assetclass field in the my file_upload view and suddenly I was able to import the data into the database. The reason for the error was that the assetclass field had a max_length=25 while the string Sonstige Vermögensgegenstände has a length of 30 characters. So although django was telling me the problem was related to the field performance_exccy actually it was due to the assetclass field.

DataError: value too long for type character varying(1024) TextField

value too long for type character varying(1024) is a PostgreSQL error, which indicates your application is trying to insert data into a VARCHAR(1024) column. However your table definition doesn't have a column which matches this definition, so I'm wondering if the application is actually trying to insert the data into a different table (for example a table with the same name in a different schema, or even a different database to the one you think it's connecting to).

The following query should identify any VARCHAR(1024) columns and provide more clues as to where the application is trying to insert data:

SELECT table_schema, table_name, column_name
  FROM information_schema.columns
 WHERE data_type = 'character varying'
   AND character_maximum_length = 1024;

Note the query will only show information for the current database.

Why does this happen when I insert a date value into a table? ERROR: value too long for type character varying(30) - PostgreSQL

it seems that your 'endereco' is most probably limited to 30 characters and you are trying to insert 33 characters in that column.

You can try shortening that text and see if this works. If yes, then you should maybe rethink the max size of that column in the table.

DatabaseError: value too long for type character varying(100)

I can bet money you have a models.SlugField without length set. The default length is 50 characters, most likely it's not enough for your use case.

Change it to models.SlugField(max_length=255) and migrate your database schema.

Value too long for type character varying(x) though my string is within range

I figured it out.

If you get this error you should check the local variables as you trace the error. For me, I found out that when my phone number is saved, it saved with parentheses so it actually went over the 12 character limit.

I wanted to save: +13434344343 which is 12 chars

But it was saved like this: (343) 434-4343 is 14 chars long

I had to change my Django settings.py

PHONENUMBER_DB_FORMAT = "E164"
PHONENUMBER_DEFAULT_REGION = "US"

---

Related Topics