Menu

non-Roman characters/dB collation

Help
macalter
2010-01-05
2013-05-30
  • macalter

    macalter - 2010-01-05

    My database info:

        MySQL charset: UTF-8 Unicode (utf8)
        Tables Collation column = latin_swedith_ci
        in PGV setup "Use the database to provide UTF-8 colation = YES

    Other threads I've read say I need to have UTF-8 for non-Roman characters (I want Polish) and have no problems when export/import is done. 

    I just went to look at my Database Connection and see this in red:

    > Your current database configuration is
    > bad. Please check your database
    > connection parameters and configure
    > again. SQLSTATE  Access
    > denied for user
    > 'user@servername.mydomain.com' (using
    > password: NO)

    What's wrong, how do I fix it?

     
  • macalter

    macalter - 2010-01-05

    I thought I'd better add Postscript: I **DID NOT** touch settings but was viewing them to ask question here about the subject :) Wouldn't touch w/o lots of hand-holding!

     
  • Greg Roach

    Greg Roach - 2010-01-05

    > in PGV setup "Use the database to provide UTF-8 colation = YES

    > I DID NOT touch settings

    This setting defaults to NO, so if you didn't, someone did!  This is a good setting to use (I recommend that everybody uses it!), however you should only select it in two circumstances:

    1) A new installation, before you create any tables

    2) An existing installation, where you have converted your tables, columns and data from the existing collation to UTF.  My utility in the patches tracker helps you do this.

    Changing it on an existing installation can result in your non-ascii characters being corrupted, your peformance falling off a cliff, or PGV simply not working.

    The help text for this item uses bold, red text for the warning!

     
  • macalter

    macalter - 2010-01-05

    Fish - the "Use database…"  Yes, I did overwrite initial NO but can't remember if at initial install or during past upgrade. Am thinking initial or maybe read instructions at time of upgrade from 4.1.5. to next version.

    Oh yes, I saw the bold. I saw the red. I no touch. I currently do not have not have, knowingly, non-ASCII. For Polish city names I use Roman characters but thought I should use proper ones. I'd rather live w/o if I'm going to break something.

    However, have I already broke something given the message I'm seeing? Not seen this when I viewed settings for SMTP not that long ago.

     
  • Greg Roach

    Greg Roach - 2010-01-05

    Not being able to connect to the DB is unrelated to the collation settings.  These don't apply until after the connection is established.

    Review your DB username/password/host/post/etc. settings.  These things tend not to stop working for no reason.  Something will have changed - either in PGV's config or the DB server config.

     
  • macalter

    macalter - 2010-01-06

    Sorry to bother but I'm really worried about the error I'm seeing. How bad is it?

     
  • Greg Roach

    Greg Roach - 2010-01-06

    <<Sorry to bother but I'm really worried about the error I'm seeing. How bad is it?>>

    Give us some more clues.  You haven't said whether your entire site is down, or you only get this error in the install wizard.

    If just the latter, read my post yesterday about web-browsers autocompleting password fields on the install wizard.

     
  • Anonymous

    Anonymous - 2010-01-06

    Mac, its serious enough. It will prevent your site from functioning.

    Do as Greg suggested and check you config.php settings for DBNAME, DBUSER and DBPASSWORD. Check that these are still the same as you started with (you would have been given them by your web host. Then check with your web host to see if they have changed something their end.

    As Greg said, these things DON'T change them selves, so if you haven't (and I have no doubt you didn't) then your web host must have.

    Also note Greg's other comment "Not being able to connect to the DB is unrelated to the collation settings." It is NOT related to collation, or Polish characters. It is simply an error in the DB connection parameters - its name, username, and password or something related to them.

     
  • macalter

    macalter - 2010-01-06

    My username/password work as I was logged into my web host and myPhpAdmin viewing the database and exporting. Last I was at Install WIz was to change my email address for SMTP. That wasn't that long ago. DOn't recall seeing the error as I'd have posted.

    My site is totally functioning. If I'd not gone to view the UTF-8 thing, probably would not have known this problem existed.

    Just looking again, database info is not there in Install Wiz. It's gone except for Database Host name. Will enter again and come back

     
  • Greg Roach

    Greg Roach - 2010-01-06

    > My site is totally functioning.
    >
    > Will enter again and come back

    If your site is working, there is no need to go back and change anything!

     
  • macalter

    macalter - 2010-01-06

    That error being there must indicate something wrong. And now I see BLANK fields. Except for my database name. I just emailed my web host support as when I viewed the tables, all showed as 1k. That's impossible.

    I'm also questioning the prefix to my tables. PGV says it's one thing, my tables show another. My _faint_ recollection is I messed up 4.1.5 and started over with new database and tables. Old pgv_ and new pgvsample_ except I now only find pgv_ on web host but pgvsample_ typed into PGV. No port, no username, use UTF-8 is set to YES.

    I upgraded to 4.2.3 last week. How would that be possible if there was anything wrong? DOn't really want to ignore this error in case it comes back to haunt me. My mind is blank whether I saw 1k for all Tables when I did backup (export) but given the total is 20k, they must have been.

     
  • Greg Roach

    Greg Roach - 2010-01-06

    Mac - calm down.

    I'm at work, so can't check the code right now, but IIRC the form blanks out the username/password for security, and you need to re-enter them if you want to change any of the settings.  Therefore blank fields are OK - especially if, as you say, your site is running.

    Next, it is perfectly normal for your tables to be 1K.  If you've used the InnoDB storage engine (a mysql option, and IMHO a good one to use), then these files will, by default, only contain the table definitions and not hte data, which is stored elsewhere.

    Think about it, if your site is running, then the data really must be there!

    If you really want to check the connection settings, look at the values stored in config.php.  These are the only ones that matter!

    If you really want to check your data is there, use a tool such as phpMyAdmin to browse your database.

    Greg

     
  • macalter

    macalter - 2010-01-06

    Okay. Error is gone. Only remaining "problem" is th SMTP stopped working. Will open new thread. I viewed config.php and all fields are completed. I'm still confused about my entry for prefix. If I've entered it to be pgvsample_ and when I'm at myhost and it doesn't show…

    I'm not touching so long as it's okay for that to be that way and if I were to need the export, it would work.

     

Log in to post a comment.