Subject | Re: [ib-support] Re: Case Sensitivity on Indices |
---|---|
Author | Martijn Tonies |
Post date | 2003-01-16T08:46:25Z |
Hi Darryl,
what runs on Linux run on Windows run on Solaris.
you use the original column so the user sees everything in proper case.
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> >Firebird DOES have an easy solution to implementBesides, IB/Fb claims to be (server-wise) platform independent-
> >case-insensitive indexes: you define the index
> >with a case-insensitive collation order.
> >The catch is...
>
> ...significant if the platform you're developing on doesn't have it.
> The solution starts losing its "easyness" if your platform doesn't
> have any case-insensitive collations.
what runs on Linux run on Windows run on Solaris.
> >The argument that Firebird should bend itsAhum - you don't SHOW that column, you just use it. For display,
> >implementation of case-insensitive indexing to align
> >with inferior and less flexible implementations
> >in competitor products appears specious to me.
>
> All of my data is in proper case. I FIND DATA THAT IS IN ALL UPPER
> CASE TO BE HARD TO READ AND UNPROFESSIONAL LOOKING. I'm not sure I
you use the original column so the user sees everything in proper case.
> understand how writing triggers to duplicate data in all upper caseDon't tweak the WHERE clause - use Views and query those.
> and changing the number of columns in a table each time you want to
> add an index is a superior and more flexible implementation. The data
> from my inferior DB2, MSSQL and Oracle databases comes back plenty
> fast for my needs. I just don't like the $$$ associated with them. I
> would rather user FB. I like Linux. I like open source.
> If I wanted to port this to another database, I would just port the
> primary tables. I wouldn't port the *_Index tables or the triggers.
> Instead of a trigger I would just add an (inferior) case-insensitive
> index to my primary table and tweak the WHERE clause of each of my
> SELECT statements to remove the join. This would be a fairly straight-
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."