Re: jpetstore: port to UNIX?
Typically, on UNIX systems, MySQL is only case-sensitive w/r/t table names, not column names. This is because MySQL maps a table name to a file on the file system, which is typically case-sensitive on UNIX systems. Brice On Fri, 28 Jan 2005 19:08:27 -0600 (CST), Ken Simpson [EMAIL PROTECTED] wrote: Hi - has anyone ported JPetStore 4 to MySQL 4.1.x and Tomcat 5.5.4 under UNIX - from whence it came? It appears to be a question of using the case on the SQL commands consistently. For instance, the MySQL schema creates a database 'JPETSTORE' with upper case, and the 'account' table and columns with lower case create table account ( userid varchar(80) not null, email varchar(80) not null, firstname varchar(80) not null, lastname varchar(80) not null, status varchar(2) null, addr1 varchar(80) not null, addr2 varchar(40) null, city varchar(80) not null, state varchar(80) not null, zip varchar(20) not null, country varchar(20) not null, phone varchar(80) not null, constraint pk_account primary key (userid) ); but the sqlmapdao generates a mapping for upper case column names sqlMap namespace=Account typeAlias alias=account type=com.ibatis.jpetstore.domain.Account/ resultMap id=accountResult class=account result property=username column=USERID/ result property=email column=EMAIL/ result property=firstName column=FIRSTNAME/ result property=lastName column=LASTNAME/ result property=status column=STATUS/ result property=address1 column=ADDR1/ result property=address2 column=ADDR2/ result property=city column=CITY/ result property=state column=STATE/ result property=zip column=ZIP/ result property=country column=COUNTRY/ result property=phone column=PHONE/ result property=languagePreference column=LANGPREF/ result property=favouriteCategoryId column=FAVCATEGORY / result property=listOption column=MYLISTOPT / result property=bannerOption column=BANNEROPT / result property=bannerName column=BANNERNAME / /resultMap [snip] -- Ken
RE: jpetstore: port to UNIX?
I wrestled with this issue awhile ago... There is a MySql startup parameter that can remove the case-sensitivity. However, all it did (if I remember correctly) was a toUpper() on the table names; so it wasn't truly case insensitive. Also, this was all in MySql 3.x So I'm not sure if the same limitations apply today; or the same work arounds. -Original Message- From: Brice Ruth [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 10:28 AM To: ibatis-user-java@incubator.apache.org Subject: Re: jpetstore: port to UNIX? Typically, on UNIX systems, MySQL is only case-sensitive w/r/t table names, not column names. This is because MySQL maps a table name to a file on the file system, which is typically case-sensitive on UNIX systems. Brice On Fri, 28 Jan 2005 19:08:27 -0600 (CST), Ken Simpson [EMAIL PROTECTED] wrote: Hi - has anyone ported JPetStore 4 to MySQL 4.1.x and Tomcat 5.5.4 under UNIX - from whence it came? It appears to be a question of using the case on the SQL commands consistently. For instance, the MySQL schema creates a database 'JPETSTORE' with upper case, and the 'account' table and columns with lower case create table account ( userid varchar(80) not null, email varchar(80) not null, firstname varchar(80) not null, lastname varchar(80) not null, status varchar(2) null, addr1 varchar(80) not null, addr2 varchar(40) null, city varchar(80) not null, state varchar(80) not null, zip varchar(20) not null, country varchar(20) not null, phone varchar(80) not null, constraint pk_account primary key (userid) ); but the sqlmapdao generates a mapping for upper case column names sqlMap namespace=Account typeAlias alias=account type=com.ibatis.jpetstore.domain.Account/ resultMap id=accountResult class=account result property=username column=USERID/ result property=email column=EMAIL/ result property=firstName column=FIRSTNAME/ result property=lastName column=LASTNAME/ result property=status column=STATUS/ result property=address1 column=ADDR1/ result property=address2 column=ADDR2/ result property=city column=CITY/ result property=state column=STATE/ result property=zip column=ZIP/ result property=country column=COUNTRY/ result property=phone column=PHONE/ result property=languagePreference column=LANGPREF/ result property=favouriteCategoryId column=FAVCATEGORY / result property=listOption column=MYLISTOPT / result property=bannerOption column=BANNEROPT / result property=bannerName column=BANNERNAME / /resultMap [snip] -- Ken
jpetstore: port to UNIX?
Hi - has anyone ported JPetStore 4 to MySQL 4.1.x and Tomcat 5.5.4 under UNIX - from whence it came? It appears to be a question of using the case on the SQL commands consistently. For instance, the MySQL schema creates a database 'JPETSTORE' with upper case, and the 'account' table and columns with lower case create table account ( userid varchar(80) not null, email varchar(80) not null, firstname varchar(80) not null, lastname varchar(80) not null, status varchar(2) null, addr1 varchar(80) not null, addr2 varchar(40) null, city varchar(80) not null, state varchar(80) not null, zip varchar(20) not null, country varchar(20) not null, phone varchar(80) not null, constraint pk_account primary key (userid) ); but the sqlmapdao generates a mapping for upper case column names sqlMap namespace=Account typeAlias alias=account type=com.ibatis.jpetstore.domain.Account/ resultMap id=accountResult class=account result property=username column=USERID/ result property=email column=EMAIL/ result property=firstName column=FIRSTNAME/ result property=lastName column=LASTNAME/ result property=status column=STATUS/ result property=address1 column=ADDR1/ result property=address2 column=ADDR2/ result property=city column=CITY/ result property=state column=STATE/ result property=zip column=ZIP/ result property=country column=COUNTRY/ result property=phone column=PHONE/ result property=languagePreference column=LANGPREF/ result property=favouriteCategoryId column=FAVCATEGORY / result property=listOption column=MYLISTOPT / result property=bannerOption column=BANNEROPT / result property=bannerName column=BANNERNAME / /resultMap [snip] -- Ken
