Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>By specifying the column as <code>VARCHAR(500)</code> 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.</p> <p>If you don't want one, use an unqualified <code>VARCHAR</code>, or use the <code>TEXT</code> type.</p> <p><code>varchar</code> and <code>text</code> are limited in length only by the system limits on column size - about 1GB - and by your memory. However, adding a length-qualifier to <code>varchar</code> sets a smaller limit manually. All of the following are largely equivalent:</p> <pre><code>column_name VARCHAR(500) column_name VARCHAR CHECK (length(column_name) &lt;= 500) column_name TEXT CHECK (length(column_name) &lt;= 500) </code></pre> <p>The only differences are in how database metadata is reported and which SQLSTATE is raised when the constraint is violated.</p> <p>The length constraint is not generally obeyed in prepared statement parameters, function calls, etc, as shown:</p> <pre><code>regress=&gt; \x Expanded display is on. regress=&gt; PREPARE t2(varchar(500)) AS SELECT $1; PREPARE regress=&gt; EXECUTE t2( repeat('x',601) ); -[ RECORD 1 ]----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ?column? | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx </code></pre> <p>and in explicit casts it result in truncation:</p> <pre><code>regress=&gt; SELECT repeat('x',501)::varchar(1); -[ RECORD 1 ] repeat | x </code></pre> <p>so I think you <em>are</em> using a <code>VARCHAR(500)</code> column, and you're looking at the wrong table or wrong instance of the database.</p>
    singulars
    1. This table or related slice is empty.
    1. POStrange PostgreSQL "value too long for type character varying(500)"
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCraig Ringer
    1. USCraig Ringer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStrange PostgreSQL "value too long for type character varying(500)"
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI'm using type text look at the description column
      singulars
      1. PO
      1. USParham
    2. CO@Parham I see that. The explanation remains relevant; `varchar(500)` is being used somewhere. Please show the actual query in your question so we can see the query that's failing. If you can't get it from Django, get it from the PostgreSQL log files and edit your question to add the query to the question. You might need to set `log_statement = 'all'` in `postgresql.conf` and reload PostgreSQL if the full query text isn't logged alongside the error.
      singulars
      1. PO
      1. USCraig Ringer
    3. COI just checked the log files as you suggested it turns out that the error was occurring when another related field was being saved
      singulars
      1. PO
      1. USParham
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload