Subject | Re: [IBO] Creating Database on the Fly Part Deux |
---|---|
Author | Paul Schmidt |
Post date | 2001-07-19T21:03:37Z |
Lucas:
On 19 Jul 2001, at 21:45, Lucas Franzen wrote:
> > Now, here is what I need, say they have a doofus at the Montreal
> > office who is bound and determined to type Montrèal or is it
> > Montréal I can never remember which one is correct. I want them all
> > considered the same. It would be really nice if the database
> > considered them equal as in:
> >
> > SELECT * FROM CUSTOMER WHERE CITY = 'Montreal', will also find
> > 'Montrèal' or 'Montréal', but I can work around it, by capturing the
> > keyboard input and stuffing the proper character in, but I would
> > rather not do that.
>
> Fortunately in german we don't have to mess around with accents (´`^)
> so I'm not sure about this one.
>
Fortunately in English we don't either, I just didn't want to have to
trap the #@$!% accents on 1500 controls. So better if I could ignore
them.
> And it will be depending on the way the users are searching.
>
> To give you an example.
> In german we have the Umlaute (äöü), which should be treated as ae,
> oe, ue. But they are ordered like 'a', 'o', 'u'.
>
> So when you're searching for a record with (for example) 'STARTING
> WITH' you'll get the 'ä' when you enter it. But if you're searching by
> a lookup-combo and the field is collated PXW_INTL850 you'll find it as
> well when entering 'ä' as well as 'a'.
>
I'll try it, I just hope I don't have to add the collation order to
every one of 10,000 varchar fields :-(
> Go ahead and try with a test-database (and if you do so, send the
> results to Thomas St. (don't dare more letters at the moment, they
> might be wrong again *g*) maybe he'll become the absolute
> collation-guru that way).
>
> Or Jason might decide to cancel 5 hours more of sleep (that's almost
> his weekly budget) and offer a A-CLASS solution *ggg*
>
> But don't be afraid: I think IBO5 will have a "UseTimeWarpForSleep"
> property.
>
This is to counteract the following, which MUST be in the Windows
kernel code somwehere.
if (time_spent < time_should_take * 147)
show_blue_screen_of_death(some_random_unrelated_error_code);
Paul Schmidt,
Tricat Technologies
Email: paul@...
Website: www.tricattechnologies.com