Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/GEOS-259
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GEOS-259
Summary: Strings not stored completely in DB
Type: Bug
Status: Open
Priority: Critical
Original Estimate: 1 day
Time Spent: Unknown
Remaining: 1 day
Project: GeoServer
Components:
WFS
Versions:
1.2.3
Assignee: Chris Holmes
Reporter: Thijs Brentjens
Created: Tue, 14 Dec 2004 7:27 AM
Updated: Tue, 14 Dec 2004 7:27 AM
Environment: Oracle 10g (OCI), Geoserver 1.2.3
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira