Re: [h2] Re: IGNORECASE=TRUE and comparing strings

2013-12-12 Thread Max Sidnin
Hi, COLLATION is a nice working solution. Thank you. And thanks for already fixed issue https://groups.google.com/forum/#!topic/h2-database/LjcgA4Ier7Q Regards, Max On Thursday, December 12, 2013 9:40:36 AM UTC+2, Thomas Mueller wrote: > > Hi, > > Sorry for the delay. Maybe "set collation" cou

Re: [h2] Re: IGNORECASE=TRUE and comparing strings

2013-12-11 Thread Thomas Mueller
Hi, Sorry for the delay. Maybe "set collation" could be used? set collation en strength primary; create table test(id int, name varchar); insert into test values(1, 'Text'); select * from test where name = 'text'; select * from test where name like '%text%'; See also http://h2database.com/html/g

Re: [h2] Re: IGNORECASE=TRUE and comparing strings

2013-11-08 Thread Max Sidnin
Hi, sorry for the late response. Could you describe the real scenario please? > For example we have next table with "ignorecase=true": +-++ | *Prefix* |*Name*| +-++ | Mr. | Max | +-+--

Re: [h2] Re: IGNORECASE=TRUE and comparing strings

2013-10-31 Thread Thomas Mueller
Hi, The option "ignorecase=true" will convert all column that are created as "varchar" to "varchar_ignorecase". I think the problem is that text literals are still interpreted as varchar, not varchar_ignorecase, so that if you compare text literals with other text literals, this is still case sens

[h2] Re: IGNORECASE=TRUE and comparing strings

2013-10-30 Thread Max Sidnin
H2 version is 1.3.174 Full connection string is: ;LOG=1;MVCC=TRUE;PAGE_SIZE=16384;CACHE_TYPE=TQ;ALIAS_COLUMN_NAME=TRUE;IGNORECASE=TRUE;MAX_MEMORY_ROWS=10;DB_CLOSE_DELAY=0;CIPHER=AES;CACHE_SIZE=4;MAX_OPERATION_MEMORY=2000; -- You received this message because you are subscribed to t