[opencms-dev] RV: Beta 2 - case-sensitiveness in MySQL 4
Claus Priisholm
cpr at codedroids.com
Mon Apr 18 08:48:24 CEST 2005
I was merely stating that Alkacon is not to blame for the poor
cross-platform experience provided by MySQL. As it was stated in the
original question the problem came about when they moved an existing
database from one MySQL server to another - a step that must be taken
with care when it involves moving from one type of filesystem to
another.
Of course if 6b2 cannot install or run out of the box on a
case-sensitive MySQL then I would say it is a problem that should be
fixed. As I am always using MySQL in case-insensitive mode I cannot
comment on that setup, but neither was the original post as they were
moving an existing database rather than installing 6b2 from scratch.
On 17/4-2005, at 19.26, Geoff Winkless wrote:
> Claus Priisholm wrote:
>
>> Great that it works for you now
>>
>> Most of the SQL statements are per default written as upper case in
>> the source code, so I don't think it is considered a bug.
>> Maybe one could blame mysql for not making case insensitivity the
>> default since it is their choice to depend on the underlying
>> filesystem as far as table-naming goes.
>
>
> So you're saying you don't think the system should be fixed, even
> though it will cause no problems to anyone else and will stop this
> occurring for some other poor sod who just happens to have a
> case-sensitive database? Nice attitude, dude.
>
> Geoff
>
>
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please
> visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
>
>
--
Claus Priisholm, CodeDroids ApS
+45 48 22 46 46
email: cpr (you-know-what) interlet.dk - cpr (you-know-what)
codedroids.com
skype: claus_priisholm
http://www.interlet.dk - http://www.codedroids.com
More information about the opencms-dev
mailing list