Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 115938 - Nearly every use of StringLenghtValidationListener is wrong on Oracle
Nearly every use of StringLenghtValidationListener is wrong on Oracle
Product: Red Hat Web Application Framework
Classification: Retired
Component: ui (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
Depends On:
  Show dependency treegraph
Reported: 2004-02-17 04:56 EST by Daniel Berrange
Modified: 2007-04-18 13:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-02 13:33:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Berrange 2004-02-17 04:56:23 EST
Description of problem:
The Bebop StringLengthValidationListener checks the length of a string
parameters in characters to ensure it does not exceed a specified
limit. Practically every single form in WAF is then used to create a
DomainObject in the DB. While on PostgreSQL VARCHAR fields are
measured in characters, on Oracle the default setting is to measure in
bytes. Thus if there is a VARCHAR(200) field and the user enters 200
Thai characters, this will likely come out at more like 600 bytes,
thus totally overflowing the data type in oracle.

We should either create a new DBStringLengthValidationListener that
measures using the size units of the current configured DB, or modify
existing StringLengthValidationListener. If the former, we will have
to additionally search & replace neearly every single occurrance of

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a new CMS Item
2. Enter 200 characters of Thai
3. Save the form
Actual results:

Expected results:
Validation warning

Additional info:

See Vadim's posting:

Comment 1 Daniel Berrange 2006-09-02 13:33:47 EDT
Closing old tickets

Note You need to log in before you can comment on or make changes to this bug.