Update of /cvsroot/monetdb/sql/src/test/bugs/Tests
In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv4851/src/test/bugs/Tests

Modified Files:
        zero_or_one_bug.stable.out 
Log Message:
propagated changes of Sunday Jul 19 2009 - Monday Jul 20 2009
from the May2009 branch to the development trunk

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2009/07/19 - nielsnes: src/test/bugs/Tests/zero_or_one_bug.stable.out,1.7.2.1
applied (adapted) utf8 patch

it fixes utf8 strings lengths, ie we now return number of unicode characters
not number of bytes.
NULL now all have a length of 0 characters
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Index: zero_or_one_bug.stable.out
===================================================================
RCS file: /cvsroot/monetdb/sql/src/test/bugs/Tests/zero_or_one_bug.stable.out,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- zero_or_one_bug.stable.out  3 Mar 2009 00:48:34 -0000       1.7
+++ zero_or_one_bug.stable.out  20 Jul 2009 13:57:50 -0000      1.8
@@ -36,7 +36,7 @@
 % .,   .L6 # table_name
 % isnull_not_isnull_id1,       L6 # name
 % int, varchar # type
-% 1,   1 # length
+% 1,   0 # length
 [ 1,   NULL    ]
 [ 2,   NULL    ]
 [ 3,   NULL    ]
@@ -49,7 +49,7 @@
 % .,   .L11 # table_name
 % isnull_not_isnull_id1,       my_col1 # name
 % int, varchar # type
-% 1,   1 # length
+% 1,   0 # length
 [ 1,   NULL    ]
 [ 2,   NULL    ]
 [ 3,   NULL    ]


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Monetdb-sql-checkins mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-sql-checkins

Reply via email to