Strings not stored completely in DB

Description

Some (long?) strings are not saved completely, but some are broken when storing in the database, e.g. the element

<scs:OMLEIDINGID>D11DAC13-CF1A-B2C9-CA6A02BCD013D6AD</scs:OMLEIDINGID>

is stored as '-CA6A02BCD013D6AD' in the database.

The strange thing is that the same value for the string, in the same transaction (but to insert another feature) is stored correctly.

I'll attach an example transaction and the data that is stored in the OMLEIDINGGEODATA table.

Environment

None

Activity

Show:
codehaus
April 10, 2015, 4:19 PM

CodeHaus Comment From: thijsbrentjens - Time: Tue, 14 Dec 2004 07:30:04 -0600
---------------------
<p>Sorry for the formatting, it is a dump of an automatically generated request. Anyway, the elemen &lt;scs:OMLEIDINGID&gt; contains the same value for each new feature ('D11DAC13-CF1A-B2C9-CA6A02BCD013D6AD').</p>

codehaus
April 10, 2015, 4:19 PM

CodeHaus Comment From: thijsbrentjens - Time: Tue, 14 Dec 2004 07:38:54 -0600
---------------------
<p>The file dumpTransactionResultDB.csv contains a dump of the results of the transaction in the database. Note that for one row (feature) the value in OMLEIDINGID is only a part of the value as stated in the transaction.</p>

codehaus
April 10, 2015, 4:19 PM

CodeHaus Comment From: cholmes - Time: Wed, 18 Jul 2007 09:51:27 -0500
---------------------
<p>This issues goes way, way back, and it looks like an issue that supercedes this was fixed, so I'm going to close it.</p>

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

None

Affects versions

Components

Priority

High
Configure