Re: NoClassDefFoundError

2016-02-25 Thread Jeff Schmitz
And you would guess right. After doing a chown -R _appserver on the Webojects Installation (/opt/Library/WebObjects) it started working. Thanks for the help! Jeff > On Feb 24, 2016, at 9:19 PM, Steve Peery wrote: > > I would guess a permissions issue. Can everything write to the log directo

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Jon Nolan
We store all email addresses in their own table. There are many reasons why this works for us and many why it might not make sense for others. Anyway, what this gives us is the ability to store related email address information in context and, specifically, that’s where our solution comes in u

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Paul Hoadley
Hi Ted, On 26 Feb 2016, at 10:39 am, Theodore Petrosky wrote: > I’ve been following this conversation, quite interesting. But, and this is > just a question for the conversation. Is there any reason when the user > registers that the user name (email address) isn’t folded into lowercase and >

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Theodore Petrosky
I’ve been following this conversation, quite interesting. But, and this is just a question for the conversation. Is there any reason when the user registers that the user name (email address) isn’t folded into lowercase and stored that way? I might be missing something very obvious (as is usual

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Paul Hoadley
On 25 Feb 2016, at 10:43 am, Paul Hoadley wrote: > Can anyone suggest a better way? What I really need is a > CaseInsensitiveEquals qualifier, like Java’s equalsIgnoreCase(). Is there > such a thing? Would it be easily implemented? Thanks for all the replies on this thread—much appreciated. Th

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Patrick Middleton
Hi folks, my experiences of this are with a release of Sybase where case-insensitive prefix searching of indexed columns caused table-scanning of a very big table, and assorted releases of MySQL with case-insensitive collation sequences. I used to use the EOEditingContext delegate API to spo

Re: Apache 2.4 WebObjects adaptor for CentOS 6 i86_64

2016-02-25 Thread Laurence Mills-Gahl
Stéphan, Have you succeeded in your installation? I just went through (and am going through) a deploy on CentOS7 64 using Apache 2.4. I added my notes to the wiki page https://wiki.wocommunity.org/display/documentation/Installing+a+deployment+environment+on+RedHat,+CentOS+or+Amazon+Linux Some

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread OC
Samuel, thanks a lot. D'oh, I definitely should have noticed (and checked) the other application! My bad. All the best, OC On 25. 2. 2016, at 19:10, Samuel Pelletier wrote: > Hi OC, > > Case insensitivity are locale specific, there is no such thing as universal > case insensitive. The built

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Samuel Pelletier
Hi OC, Case insensitivity are locale specific, there is no such thing as universal case insensitive. The built in case insensitive is only for a-z and A-Z. I build a collation file for latin accents where all e are equals (eéèêëEÉÈÊË), same for o and i and cçCÇ. It is attached to this message.

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Morris, Mark
Hi Samuel, That’s certainly a possibility we’ve talked about, and for sure it would improve the performance vs. my solution. The tradeoffs to consider are that we have many columns across many tables where this is used, with 100’s of millions of records, and so each new index is a huge chunk of

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread OC
Ha, this reminds me of one old problem I've bumped into and did not find a solution yet. FrontBase contains a CaseInsensitive.coll1 collation file, which would work just about perfectly... if it supported all accounted characters. Alas, it does not; therefore, whilst a case insensitive like wit

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Samuel Pelletier
Hi Mark, I suggest you look into adding a collation to your column or index. I do not know how Oracle does this but it surely exists. With an index using a collation, your query is trivial and much more efficient because the index is already case insensitive, there is no OR. A query like the o

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Morris, Mark
If there’s interest, perhaps I could try to see about adding it as an ERX qualifier. Most of the optimizations have to do with streamlining in cases where a character in the search term is non-alpha, and getting the greatest number of characters in the hit with only 4 terms in the OR. — Mark O

Re: Use case for a "case insensitive equals" qualifier

2016-02-25 Thread Morris, Mark
Hi Lon, We run into this a lot, and I have a rather complex solution for a “case insensitive begins with” qualifier that actually works well, at least with Oracle and its indexing. My method returning this qualifier is actually about 60 lines, but most of that is optimizations for special cases