On Jul 30, 2011, at 2:00 AM, Lachlan Deck wrote: > To do it correctly it would be a property (I think) as it assumes you've used > MySQLs default of case-insensitiveness which is probably true for most people > but perhaps not all.
Well, when you put it that way, yeah, you're both right (^_^) > > I didn't get around to contributing it last year after contributing the > H2Plugin as others like Ramsey were working on the MySQL plugin at the time. > I think I mentioned at the time what I'd done which was using the 'binary' > keyword for case-sensitive (both for where clauses and sort orderings) and > plain old like clauses for insensitive (without the UPPER) - but it was > obviously missed along the way. > > I've now taken my MySQLExpression class, tied it in optionally, and sent a > pull request from a github topic branch for others to review and make use of > and _test_. > > I've not had opportunity to use WO over the last 16 months :-/ but the source > for the plugin I was using was lying around awaiting use :). > > Lachlan Deck > lachlan.d...@gmail.com > > On 30/07/2011, at 12:41 AM, Ramsey Gurley wrote: > >> I don't think it would be a property. That would just be the correct >> behavior. I wasn't aware of such syntax when I wrote the initial MySQL >> plugin for wonder, or I would have certainly included this. I dug through >> the manual trying to solve this problem but never found the answer. >> >> I don't use MySQL anymore tho, so if you want it fixed, submit a patch/pull >> request. >> >> Ramsey >> >> On Jul 29, 2011, at 7:00 AM, Johann Werner wrote: >> >>> >>> Am 29.07.2011 um 12:54 schrieb Lachlan Deck: >>> >>>> What are the replication possibilities these days for dbs such as Postgres >>>> et al? >>>> Part of the success of MySQL I gather is having this support. >>>> >>>> We unfortunately use MySQL where I'm working, and it certainly struggles >>>> for certain things. One of the things that kills mysql as well is >>>> refactoring on large tables. e.g., adding columns causing a full table >>>> copy etc. This has been fixed apparently in 5.5. >>>> >>>> So far as poor indexing usages, WO by default doesn't help for >>>> case-insensitive searches by its usage of "like UPPER(..)" which bypasses >>>> mysql indexes altogether. I don't know if more recent Wonder mysql >>>> adaptors help with this but I'd created a custom adaptor for mysql that >>>> essentially did the following: >>>> - for case-insensitive: ... a like 'Foo' >>>> - for case-sensitive: binary a like 'Foo' >>> >>> where is the commit for the current MySQL plugin and the corresponding >>> property to switch to the new behavior? ;-) >>> >>> >>>> >>>> Lachlan Deck >>>> lachlan.d...@gmail.com >>>> >>>> <snip> >>>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/webobjects-dev/ramseygurley%40gmail.com >>> >>> This email sent to ramseygur...@gmail.com >> >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
