Incorrect table name 'cpg148_sessions' Incorrect table name 'cpg148_sessions'
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Incorrect table name 'cpg148_sessions'

Started by dreamhao, July 24, 2006, 03:34:29 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

dreamhao

Hi,

I just installed the cpg1.48, but I can't open the page.

problem:
------------------------------------------------
While executing query "delete from `ccge.ch`.cpg148_sessions where time<1153744109 and remember=0;" on Resource id #5

mySQL error: Incorrect table name 'cpg148_sessions'
------------------------------------------------

Anyone knows what's happened.
http://www.ccge.ch/photo/

Thanks in advance

Nibbler

Yup, dots are not allowed in database names. Either get it changed or search the board for the workaround.

dreamhao

Because it's NT system, he(my friend) is always using the datebase with this name. And there is already a lots datebase inside, that will be difficult to chage it...

Do you have another solution?

Nibbler

Yes, read the part of my reply that follows the word 'or' for the other solution.

Joachim Müller

However, your friend should get this fixed imo, as it's against the mysql specifications to have a dot in the database name or table name. In mysql, the dot is being used for other purposes, that's why. He may run into similar issues later (with other apps) even if you do as Nibbler suggested and apply the workaround.

dreamhao

"search the board for the workaround."

Please tell me how to do exactly, I'am newbie.

Joachim Müller

Use the "search" button at the top of this page. Try queries like "mysql database name dot" or similar. If your search doesn't show the expected results, try rephrasing your question. That's what we'd have to do as well. What Nibbler suggested: others have posted similar issues, and Nibbler has posted a reply to one of the treads that explained a workaround. Best solution is to have the database name changed, or create another database (if you're allowed to do so) that doesn't contain a dot in the name.