2 messages in com.mysql.lists.eventum-usersRe: I think I found a bug...| From | Sent On | Attachments |
|---|---|---|
| Andrew Kopp | 19 Sep 2007 08:03 | |
| Bryan Alsdorf | 24 Sep 2007 12:54 |
| Subject: | Re: I think I found a bug...![]() |
|---|---|
| From: | Bryan Alsdorf (bry...@mysql.com) |
| Date: | 09/24/2007 12:54:01 PM |
| List: | com.mysql.lists.eventum-users |
Hi Andrew,
Andrew Kopp wrote:
Bryan/João,
First off, thanks for your great software.
Thank you for using it!
I tried installing the latest eventum several times using php 4.3.6 with
different versions of mysql... first i tried 4.0.18 but as stated on your site,
the install breaks as the utf8 bug is present.... however I still had the same
login issues when installing on a windows version of mysql 5.0.
I ended up narrowing it down to the fact that my database name began with a
number.... the auth class was throwing a sql statement error within the
userExists() function. I started to play with the sql statements, and when I
removed the APP_DEFAULT_DB part it worked fine. However since that would have
required me to remove it from all SQL statements and is probably bad practice, I
just started prepending my customers databases (named after their account
number) with a letter. Is this a bug within eventum or is it bad practice to use
numbers in your database name?
Ah, I seem to recall seeing this before. I don't think it is bad practice to begin with numbers, but it seems MySQL has problems with it.
Any thoughts?
I think one solution would be to quote the database name, i.e. add ` around the db name in eventum, such as
define('APP_DEFAULT_DB', "`42_blah`");
Can you let me know if that works?
Best Regards,
-- Bryan Alsdorf, Manager of Support Systems MySQL AB, www.mysql.com
Discover new MySQL Monitoring & Advisory features at: http://www.mysql.com/products/enterprise/whats_new.html




