History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: FC-1399
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: brian pickens
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FarCry Core Framework

mySQL tables are created in camelCase while sql code is not writen in camelCase

Created: 14/Jul/08 12:55 AM   Updated: 13/Aug/08 11:30 AM
Component/s: Installer & Updaters
Affects Version/s: FarCry 4.0 (Gonzalas), FarCry 5.0 (Fortress), 4.0.9, 4.0.10
Fix Version/s: 5.0.2

Time Tracking:
Not Specified

Environment: I am running Ubuntu 8.04 Hardy Heron, with mySQL 5.0.51, apache 2.2.8, jrun 4, and coldfusion 8


 Description  « Hide
Installation was fine, and the app ran fine until I tried to upload an image to a news piece. Upon clicking 'upload' in the image uploader, I promptly got an error saying that 'Table farcry.dmfile doesn not exist.' When this happened, I went into mySQL and renamed the table from dmFile, to dmfile. This fixed that error, but I then Upon trying the uploader again, I promptly got a similar error saying that 'Table farcry.dmflash does not exist.'

I posted this in the mail list, and someone said that all their tables were created in lowercase, but all my tables names were created in camelCase, and pretty much the rest of the app works fine.
http://groups.google.com/group/farcry-dev/browse_thread/thread/97504cac24bee220

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Geoff Bowers - 11/Aug/08 02:20 PM
This can be resovled by setting mySQL to use the flag for case insensitive tables. This is a global database setting.

I believe the underlying issue is realted to ISAM tables being stored on the file system. You may have better results using InnoDB tables instead.

Geoff Bowers - 11/Aug/08 02:22 PM
Not sure what we can do here beyond overhauling the SQL in the system, and enforcing correct casing on all future development in SQL statements. mySQL seems to be alone in this issue and there are a couple of reasonable workarounds; ie. set flag to case insensitive tables or use innoDB.

If people believe this should be reopened as a critical issue, please lobby us on the forum.