[ 
https://issues.apache.org/jira/browse/DERBY-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594458#action_12594458
 ] 

Shawn Aucoin commented on DERBY-3664:
-------------------------------------

Hmm...interesting.  I have a deep oracle development back ground and I know 
that Oracle doesn't treat it this way.  It is interesting and to me would seem 
to be a bug, because 'first_test ' and first_test' are not equal.

However, i am not going to moan about it as I think i can get the data changed, 
but i would suggest that maybe this could become a future enhancement as a 
space is really a valid character (even trailing ones) and should be included 
in comparisons, although I fully acknowledge that the data should not have 
trailing spaces, and I am hard pressed to think of a valid scenario where it 
would be appropriate to have trailing spaces in a field.

Being a developer, I don't particularly like it when something does something 
that i didn't ask it too...;)

Again, thanks for the great product!

> Trailing white space in varchar field is trimmed off.
> -----------------------------------------------------
>
>                 Key: DERBY-3664
>                 URL: https://issues.apache.org/jira/browse/DERBY-3664
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.1.3
>         Environment: Win XP, Derby 10.4.1.3
>            Reporter: Shawn Aucoin
>
> When executing an insert statement with a varchar field containing trailing 
> whitespace, the trailing whitespace is removed.  This results in unique 
> constraint issues.  If  index is not unique, select * from login where login 
> = 'first_test'  will return both records.  Preceeding whitespace doesn't 
> appear to be affected.  I tested this from IJ and from java api.  I included 
> an example below
> CREATE TABLE LOGIN
> (
>       LOGIN_ID INT PRIMARY KEY,
>       LOGIN VARCHAR(60)
> );
> CREATE UNIQUE INDEX LOGIN_LOGIN_IDX 
> ON LOGIN (LOGIN DESC);
> insert into login (LOGIN_ID, LOGIN) values (1, 'first_test');
> insert into login (LOGIN_ID, LOGIN) values (2, 'first_test ');
> Now, i fully admit that there is no logical reason for trailing whitespace, 
> but it is client data that i am dealing with and I may not be able to get it 
> changed.  Thanks, derby is a sweet product!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to