recommended upper/lower case setting for mysql

[Si Chen-2]

Hi everybody -

I just noticed that MySQL could be case sensitive in some cases.  
http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html

Given the way the entity engine works, would it be better to recommend
that it's always configured to be case insensitive for ofbiz users?

Si

[David E Jones]

Do you mean for meta-data?

For OFBiz it shouldn't really matter. Is there a more specific  
problem you've run into?

-David


On Jan 16, 2007, at 4:00 PM, Si Chen wrote:

> Hi everybody -
>
> I just noticed that MySQL could be case sensitive in some cases.  
> http://dev.mysql.com/doc/refman/5.0/en/identifier-case- 
> sensitivity.html
>
> Given the way the entity engine works, would it be better to  
> recommend that it's always configured to be case insensitive for  
> ofbiz users?
> Si

[Si Chen-2]

David E. Jones wrote:

>
> Do you mean for meta-data?
>
> For OFBiz it shouldn't really matter. Is there a more specific problem
> you've run into?
>
> -David
>
>
> On Jan 16, 2007, at 4:00 PM, Si Chen wrote:
>
>> Hi everybody -
>>
>> I just noticed that MySQL could be case sensitive in some cases.  
>> http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html
>>
>> Given the way the entity engine works, would it be better to
>> recommend that it's always configured to be case insensitive for
>> ofbiz users?
>> Si
>

Actually, believe it or not it's for the table names.  I ran into
problems moving stuff between windows, linux, and os x because the MySQL
defaults are different for each one.  I thought since that ofbiz can run
fine with case-insensitive, it might be better to recommend to everybody
to do the case-insensitive setting as a lowest common denominator.

[David E Jones]

On Jan 16, 2007, at 5:28 PM, Si Chen wrote:

> Actually, believe it or not it's for the table names.  I ran into  
> problems moving stuff between windows, linux, and os x because the  
> MySQL defaults are different for each one.  I thought since that  
> ofbiz can run fine with case-insensitive, it might be better to  
> recommend to everybody to do the case-insensitive setting as a  
> lowest common denominator.

Interesting... gotta love database quirks!

I think this is fine. I did a quick search on docs.ofbiz.org for  
"mysql" and I see mention in a number of pages, but we should really  
have something like a bunch of database how-tos, in the case a "MySQL  
How-To" page or something along those lines.

There has been a fair amount of discussion about MySQL lately with a  
number of different issues that it would be good to address in such a  
document (if a good best-practice solution exists).

BTW, for anyone reading in: I don't mean to single out MySQL here,  
and in fact I personally don't recommend that people use MySQL with  
OFBiz, especially if they need to do anything internationalized or  
the like, and I have issues with the MySQL licensing policies to some  
extend, and practices to a large extent. Anyway, my favorite  
production database for OFBiz is PostgreSQL, just in case anyone is  
wondering.

-David

[cjhowe]

I'd like to stop dealing with some of the quirks.  And
they seem to be up to something with some recent
activity..are there any decent GUI tools to mess with
Postgresql? It has an odbc so at worst case it can be
used through access.  I've been using Sqlyog for MySql
recently and I had only originally used MySql because
of phpmyadmin.

--- "David E. Jones" <[hidden email]> wrote:

>
> On Jan 16, 2007, at 5:28 PM, Si Chen wrote:
>
> > Actually, believe it or not it's for the table
> names.  I ran into  
> > problems moving stuff between windows, linux, and
> os x because the  
> > MySQL defaults are different for each one.  I
> thought since that  
> > ofbiz can run fine with case-insensitive, it might
> be better to  
> > recommend to everybody to do the case-insensitive
> setting as a  
> > lowest common denominator.
>
> Interesting... gotta love database quirks!
>
> I think this is fine. I did a quick search on
> docs.ofbiz.org for  
> "mysql" and I see mention in a number of pages, but
> we should really  
> have something like a bunch of database how-tos, in
> the case a "MySQL  
> How-To" page or something along those lines.
>
> There has been a fair amount of discussion about
> MySQL lately with a  
> number of different issues that it would be good to
> address in such a  
> document (if a good best-practice solution exists).
>
> BTW, for anyone reading in: I don't mean to single
> out MySQL here,  
> and in fact I personally don't recommend that people
> use MySQL with  
> OFBiz, especially if they need to do anything
> internationalized or  
> the like, and I have issues with the MySQL licensing
> policies to some  
> extend, and practices to a large extent. Anyway, my
> favorite  
> production database for OFBiz is PostgreSQL, just in
> case anyone is  
> wondering.
>
> -David
>
>

[Jacques Le Roux]

Chris,

pgAdmin III is a good tool for PostGres.

Jacques

----- Original Message -----
From: "Chris Howe" <[hidden email]>
To: <[hidden email]>
Sent: Wednesday, January 17, 2007 3:03 AM
Subject: Re: recommended upper/lower case setting for mysql

> I'd like to stop dealing with some of the quirks.  And
> they seem to be up to something with some recent
> activity..are there any decent GUI tools to mess with
> Postgresql? It has an odbc so at worst case it can be
> used through access.  I've been using Sqlyog for MySql
> recently and I had only originally used MySql because
> of phpmyadmin.
>
> --- "David E. Jones" <[hidden email]> wrote:
>
> >
> > On Jan 16, 2007, at 5:28 PM, Si Chen wrote:
> >
> > > Actually, believe it or not it's for the table
> > names.  I ran into  
> > > problems moving stuff between windows, linux, and
> > os x because the  
> > > MySQL defaults are different for each one.  I
> > thought since that  
> > > ofbiz can run fine with case-insensitive, it might
> > be better to  
> > > recommend to everybody to do the case-insensitive
> > setting as a  
> > > lowest common denominator.
> >
> > Interesting... gotta love database quirks!
> >
> > I think this is fine. I did a quick search on
> > docs.ofbiz.org for  
> > "mysql" and I see mention in a number of pages, but
> > we should really  
> > have something like a bunch of database how-tos, in
> > the case a "MySQL  
> > How-To" page or something along those lines.
> >
> > There has been a fair amount of discussion about
> > MySQL lately with a  
> > number of different issues that it would be good to
> > address in such a  
> > document (if a good best-practice solution exists).
> >
> > BTW, for anyone reading in: I don't mean to single
> > out MySQL here,  
> > and in fact I personally don't recommend that people
> > use MySQL with  
> > OFBiz, especially if they need to do anything
> > internationalized or  
> > the like, and I have issues with the MySQL licensing
> > policies to some  
> > extend, and practices to a large extent. Anyway, my
> > favorite  
> > production database for OFBiz is PostgreSQL, just in
> > case anyone is  
> > wondering.
> >
> > -David
> >
> >

[Joe Eckard]

You might also want to check out Aqua Data Studio ( http://
www.aquafold.com/ ) - v4.7 is free for personal use. It's cross  
platform and supports all of the major databases.

-Joe

On Jan 17, 2007, at 2:23 AM, Jacques Le Roux wrote:

> Chris,
>
> pgAdmin III is a good tool for PostGres.
>
> Jacques
>
> ----- Original Message -----
> From: "Chris Howe" <[hidden email]>
> To: <[hidden email]>
> Sent: Wednesday, January 17, 2007 3:03 AM
> Subject: Re: recommended upper/lower case setting for mysql
>
>
>> I'd like to stop dealing with some of the quirks.  And
>> they seem to be up to something with some recent
>> activity..are there any decent GUI tools to mess with
>> Postgresql? It has an odbc so at worst case it can be
>> used through access.  I've been using Sqlyog for MySql
>> recently and I had only originally used MySql because
>> of phpmyadmin.
>>
>> --- "David E. Jones" <[hidden email]> wrote:
>>
>>>
>>> On Jan 16, 2007, at 5:28 PM, Si Chen wrote:
>>>
>>>> Actually, believe it or not it's for the table
>>> names.  I ran into
>>>> problems moving stuff between windows, linux, and
>>> os x because the
>>>> MySQL defaults are different for each one.  I
>>> thought since that
>>>> ofbiz can run fine with case-insensitive, it might
>>> be better to
>>>> recommend to everybody to do the case-insensitive
>>> setting as a
>>>> lowest common denominator.
>>>
>>> Interesting... gotta love database quirks!
>>>
>>> I think this is fine. I did a quick search on
>>> docs.ofbiz.org for
>>> "mysql" and I see mention in a number of pages, but
>>> we should really
>>> have something like a bunch of database how-tos, in
>>> the case a "MySQL
>>> How-To" page or something along those lines.
>>>
>>> There has been a fair amount of discussion about
>>> MySQL lately with a
>>> number of different issues that it would be good to
>>> address in such a
>>> document (if a good best-practice solution exists).
>>>
>>> BTW, for anyone reading in: I don't mean to single
>>> out MySQL here,
>>> and in fact I personally don't recommend that people
>>> use MySQL with
>>> OFBiz, especially if they need to do anything
>>> internationalized or
>>> the like, and I have issues with the MySQL licensing
>>> policies to some
>>> extend, and practices to a large extent. Anyway, my
>>> favorite
>>> production database for OFBiz is PostgreSQL, just in
>>> case anyone is
>>> wondering.
>>>
>>> -David
>>>
>>>

[Ean Schuessler]

On Tuesday 16 January 2007 20:03, Chris Howe wrote:
> I'd like to stop dealing with some of the quirks.  And
> they seem to be up to something with some recent
> activity..are there any decent GUI tools to mess with
> Postgresql? It has an odbc so at worst case it can be
> used through access.  I've been using Sqlyog for MySql
> recently and I had only originally used MySql because
> of phpmyadmin.

I've used PostgreSQL for years and years. I was scared for a little while when
MySQL started gaining popularity but it still lacks nice little features like
the option of waiting until the end of a transaction to resolve foreign key
integrity (which is a boon).

PostgreSQL works fine with the Eclipse database tooling, if you like that GUI
kind of thing... which I do, sort of.

--
Ean Schuessler, CTO
[hidden email]
214-720-0700 x 315
Brainfood, Inc.
http://www.brainfood.com