0000027: NAME:PostgreSQL72FatalError REASON:fatal pgsql error - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0000027	SOGo	Backend Address Book	public	2009-06-18 08:02	2009-10-08 14:51

Reporter	tarjei	Assigned To	ludovic
Priority	normal	Severity	crash	Reproducibility	always
Status	resolved	Resolution	won't fix
Product Version	nightly v2

Summary	0000027: NAME:PostgreSQL72FatalError REASON:fatal pgsql error
Description	It seems that SOGO accepts adressbook entries that are too big for postgres: Jun 17 21:09:15 sogod [23420]: <0x0x97a6288[GCSFolder]> ERROR(-[GCSFolder writeContent:toName:baseVersion:]): cannot insert c ontent : <PostgreSQL72Exception: 0x9890180> NAME:PostgreSQL72FatalError REASON:fatal pgsql error (channel=<0x0x957d480[Postgr eSQL72Channel]: connection=<0x0x96706f8[PGConnection]: connection=0x0x97161c0>>): ERROR: value too long for type character varying(256) Jun 17 21:09:15 sogod [23420]: [ERROR] <0x0965F3F8[SOGoContactGCSEntry]:1D64681A-E3D6-0001-4668-11201C807DF0.vcf> write faile d: <PostgreSQL72Exception: 0x9890180> NAME:PostgreSQL72FatalError REASON:fatal pgsql error (channel=<0x0x957d480[PostgreSQL72 Channel]: connection=<0x0x96706f8[PGConnection]: connection=0x0x97161c0>>): ERROR: value too long for type character varyin g(256)
Tags	No tags attached.

Date Modified	Username	Field	Change
2009-06-18 08:02	tarjei	New Issue
2009-10-08 14:51	ludovic	Note Added: 0000145
2009-10-08 14:51	ludovic	Status	new => resolved
2009-10-08 14:51	ludovic	Resolution	open => won't fix
2009-10-08 14:51	ludovic	Assigned To	=> ludovic

ludovic 2009-10-08 14:51 administrator ~0000145	The entries get properly reject by the DB driver which can have different limits. We can't do validation as the input could also come from other clients (Thunderbird, cadaver, etc). We rely on proper DB errors and send that back to the client.