🚀 go-pugleaf

I am searching the system tables for the name of a table for a given
database. If the dialect is case-insensitive, the name passed to my function
could refer to a name which does not exactly match the name in the
appropriate system table. Therefore I have converted the name passed to
uppercase and used the UPPER keyword on the appropriate column to find the
match.

I am not sure how to use a collation driver to do the same thing.

"Jeff Overcash (TeamB)" <jeffovercash@mindspring.com> wrote in message
news:3E05D89A.88B2E141@mindspring.com...
>
>
> Edward Diener wrote:
> >
> > Thanks ! UPPER should work just fine, but I will look at collation for
> > possible international distribution.
> >
>
> The problem with UPPER is that you will lose the ability to do an indexed
> search.  It will result in an natural scan.  Collation drivers ( that are
> written correctly) will allow for case insensitive in both the order by
and
> where sections (note that many of the IB supplied ones only work in the
Order by
> section).  Another alternative is another column that triggers keep filled
out
> that uppercases the column you want and you place an index on that column
and
> search that column.
>
> > "Aage Johansen" <aagjohan@offline.no> wrote in message
> > news:3E04EBF2.1EE39FD6@offline.no...
> > > Edward Diener wrote:
> > > > When using WHERE with a CHAR or VARCHAR field, is ther a way to
specify
> > that
> > > > I want to match the value of the field with a string constant in a
case
> > > > insensitive manner ?
> > >
> > >
> > > where Upper(THEFIELD) = Upper(:TheValue)
> > >
> > > or, you might try a case insensitive collation.
>
> --
> Jeff Overcash (TeamB)
>       (Please do not email me directly unless  asked. Thank You)
> Maybe it was infatuation or the thrill of the chase.
> Maybe you were always beyond my reach and my heart was playing safe.
> But was that love in your eye I saw or the reflection of mine?
> Give me time, won't you give me that time!
> Welcome back to the circus.            (Fish)