I am enclosing a text file if this is not the correct manner let me know
whats best way its not a lot of lines.
ServerVersion: 07.03.0200 PostgreSQL 7.4.6 on i386-redhat-linux-gnu,
compiled by GCC i386-redhat-linux-gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2
ERROR: row is too big: size 9856, maximum size 8136
Joel Fradkin
Wazagua, LLC
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305
[EMAIL PROTECTED]
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, LLC. All rights reserved. WAZAGUA, LLC
This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.
-----Original Message-----
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 10:01 PM
To: Joel Fradkin
Cc: [email protected]
Subject: Re: [SQL] ERROR: row is too big: size 9856, maximum size 8136
On Wed, Jan 19, 2005 at 03:50:30PM -0500, Joel Fradkin wrote:
> I get ERROR: row is too big: size 9856, maximum size 8136 when inserting
a
> view?
Could you post the smallest possible self-contained example that
demonstrates this behavior? What version of PostgreSQL are you
using?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
CREATE OR REPLACE VIEW thenetworkcallbackview
as
select i.clientnum, i.incidentid, incidentnum, incidenttypeid,
incidentdate, subjectid, subjecttypeid, locationid, suspectedactivity.value as
description, situation, policenotified, injuries,
injurednum, injuriesdescription, propertydamage,
damagelevelid, incidentreport, i.transfered, i.transftypeid, i.transfdate,
i.transfbyid, i.transfnum,
lastmodified, createdbyid,i.isdeleted, workflowstatus,
cashloss, merchloss, totloss, markettypeid, typeofweaponid, alarmid, cameraid,
escalated, transcount, orgcalldate_time, anoncaller,
callernamefirst as firstname, callernamelast as lastname, callernamefirst || '
' || callernamelast as callernamelast, callertype, callertitle,
callerphone, callerext, callerbesttimetocall,
calleremail, clientname, location, dba, address1, address2, city, state, zip,
country, phone, ext,
abuselocation, casesource.value as hoiwincdknown,
supportdocsavailable, next24hours, nextwhen, nextwhere, howhotlineknown,
interviewernotes,
clientinstructions,
case
when i.statusid is null then 'none'
when i.statusid = 1 then 'open'
when i.statusid = 2 then 'closed'
end as status,i.assignedto,
cb.callbackdate, substring(cb.callbacknotes,1,20) as callbacknotes
from tblincident i
inner join tblincidentcallback cb on i.incidentnum = cb.incidentid and
i.clientnum = cb.clientnum
left outer join tblcasesource casesource on i.inccasesourceid = casesource.id
and (i.clientnum=casesource.clientnum)
left outer join tblsuspectedactivity suspectedactivity on
i.incsuspectedactivityid = suspectedactivity.id and
(i.clientnum=suspectedactivity.clientnum);
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
