Install Help

[greggk]

I followed all the instructions, I created the database, I called it gallery, username gallery, and password gallery.
When I load setup.php it says that I have mysql version 3.23.39 and it gives the available databases, and points out to the correct gallery database for ee.
Then it starts and I get the following error.
INSERTING CORE EE DATA:

You have an error in your SQL syntax near '`ee_camera` ' at line 2
ERROR IN QUERY:
DROP TABLE IF EXISTS `ee_camera`

I tried uploading the setup both in binary and asci, both gives me the same error, any suggestions?

[Pekka]

Try http://photography-on-the.net/ee/files/non_backquote_setup.zip

[mikenco]

I also have exactly the same problem?...

Your link above is just the installation instructions (which I read before install).

Any other ideas? :-)

[Pekka]

mikenco wrote:
I also have exactly the same problem?...

Your link above is just the installation instructions (which I read before install).

No, it's a setup file _without_ SQL backquotes around table names. The problem you see is that your server for some unknown reason can not process the `character. More about `in http://www.mysql.com/doc/L/e/Legal_names.html i.e. "Note that if the identifier is a restricted word or contains special characters you must always quote it with ` when you use it"

Try http://photography-on-the.net/ee/files/ee_test_db.zip
and you'll see the error emerge.

I'll try to find out the reason for some servers rejecting ´and what I can do about in in coding.

[Pekka]

Also, you both should check that you have all user privileges to you MySQL.

[greggk]

Well that helped a lot. I just put in the new setup file, and it installed it, quickly. Now why would my mysql not handle the `?
Is it something I should try to fix?

Thanks for the help.

[Pekka]

greggk wrote:
Well that helped a lot. I just put in the new setup file, and it installed it, quickly. Now why would my mysql not handle the `?
Is it something I should try to fix?

Thanks for the help.

No problem.

The backquote problem is something that should not happen, as it is perfectly legal and actually required notation for MySQL queries. I wish I knew why it happens - perhaps Apache does some character traslations on the fly which mess things up, perhaps the MySQL is an altered or CVS version where all does not function as told in specs.

I'll let you know as soon as I figure it out.