Graham Pearson
|
| Posted: 12/28/2004, 11:57 AM |
|
Has anyone been able to get CCS 2.3 to work with MySQL 4.1. I have
just re-loaded my computer and installed all of the latest software
which I use on a daily basis and have come up with an issue.
When I try to create a Database Connection, I get an error message
that states Client does not support authentication protocol requested
by server; consider upgrading client.
Anyone solved this issue?
|
|
|
 |
peterr
Posts: 5971
|
| Posted: 12/28/2004, 12:04 PM |
|
You may need to upgrade your client, which is the ODBC driver.
CCS itself doesn't know anything about MySQL but uses whichever ODBC driver you installed. This error message is shown by MySQL or your ODBC driver.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
 |
|
Graham Pearson
|
| Posted: 12/28/2004, 1:02 PM |
|
Does anyone know of an ODBC Driver for MySQL which will work with 4.1.
7 since MyODBC 3.51 has known problems which I have just discovered.
I am trying to finish up a CCS Online Registration Project and
currently at a Halt until I can solve this issue to complete this
project.
12/28/2004 3:04:37 PM
peterr <peterr@forum.codecharge> wrote in message
<441d1bc555fd20@news.codecharge.com>
> You may need to upgrade your client, which is the ODBC driver.
> CCS itself doesn't know anything about MySQL but uses whichever
ODBC driver you
> installed. This error message is shown by MySQL or your ODBC driver.
> _________________
> Peter R.
> YesSoftware Forums Moderator
> For product support please visit http://support.yessoftware.com
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
|
|
|
|
peterr
Posts: 5971
|
| Posted: 12/28/2004, 4:25 PM |
|
Since you need help with MySQL you may want to consider visiting MySQL Website. I just did couple quick searches there and came up with some answers:
http://forums.mysql.com/read.php?37,3001,3001
http://dev.mysql.com/doc/mysql/en/Old_client.html
Once you get through the ODBC issues you may also encounter issues with connecting to MySQL 4.1 from your scripts/programs. If you're using PHP please take a look at this:
http://forums.codecharge.com/search.php?s_keyword=mysql...[]=25&s_period=
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
bb
|
| Posted: 01/10/2005, 1:12 PM |
|
Quote :Warning: mysql_pconnect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client in c:\wwwroot\en\customersupport\db_mysql.php on line 99
Since the error actually references the CCS db_mysql.php file, this is likely to be an issue for a lot of people when they upgrade.
|
|
|
|
bb
|
| Posted: 01/10/2005, 1:21 PM |
|
no soluition yet, but here's relevant info:
http://bugs.php.net/bug.php?id=30586&edit=1
http://dev.mysql.com/doc/mysql/en/Old_client.html
|
|
|
|
peterr
Posts: 5971
|
| Posted: 01/10/2005, 1:34 PM |
|
bb,
I could be wrong, but I believe that your message is not related to the above discussion. Creating client-side database connection is one topic, while using database connection (server-side) in PHP is another. There are other forum discussions and support knowledge base article that discuss how to use server-side connection to MySQL 4.1 in CCS.
I believe that connecting on the client side requires only an appropriate ODBC driver.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
bb
|
| Posted: 01/24/2005, 10:51 PM |
|
Sorry. My info is related to the new MySQL password hashing and connecting to db's as a result of that..
|
|
|
|
marcwolf
Posts: 361
|
| Posted: 03/18/2005, 4:05 AM |
|
We are about to embark on a project that will require MySQL V 5.
As such any information on 4.1 upwards would be most benificial.
Have you been able to resolve the issue with 4.1 ans 5.x will prob have the same issues.
The reason for the move is that the client is currently running Ms-SQL 2000 with Ms Access clients. They are running about 200 terminal services but will soon launch a new aspect that will require either 3,000 terminal server licenses - or a move to a web environment. As the licensing for Ms-SQL on a web environment is fairly hight - we are turning to MySQL
We will be needing views, stored procedures, and triggers.
Many thanks for any information
Dave
_________________
' Coding Coding Coding
Keep Those Keyboards Coding.
Raw Code!!!!!!!
|
|
|
|
peterr
Posts: 5971
|
| Posted: 03/20/2005, 11:34 AM |
|
From what I've seen most people were able to make MySQL 4.1 work using the instructions provided in our KB.
I don't expect that MySQL will make any other changes that are incompatible with their previous versions because then they would force almost all Web developers that use MtSQL to make changes in their applications, which would be unreasonable. Thus I think that the authentication method was the only change made by MySQL, plus MySQL also provides instructions on how to use the old authentication method for compatibility reasons.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
GM
|
| Posted: 04/07/2005, 2:58 PM |
|
FYI,
http://dev.mysql.com/doc/mysql/en/timestamp-4-1.html
So if I upgrade from 4.0.x to 4.1.x, all PHP applications depending on the 4.0.x format of TIMESTAMP columns will break, since the documentation above for 4.1.x says, "TIMESTAMP columns are displayed in the same format as DATETIME columns." It might seem trivially easy to accomodate the changed format, but remember that many of us use numerous applications with tens of millions of lines of code written *and* maintained by others.
From my 4.0.2x MySQL, I see that indeed, many applications will break if MySQL 4.1.x changes the format of TIMESTAMP columns to that of DATETIME columns:
CREATE TABLE junk (
id smallint(5) unsigned NOT NULL auto_increment,
ts timestamp(14) NOT NULL,
dt datetime NOT NULL default '0000-00-00 00:00:00',
PRIMARY KEY (id)
) TYPE=MyISAM AUTO_INCREMENT=2 ;
--
-- Dumping data for table `junk`
--
INSERT INTO junk (id, ts, dt) VALUES (1, '20050407144506', '2005-04-07 14:45:06');
|
|
|
|
peterr
Posts: 5971
|
| Posted: 04/07/2005, 4:02 PM |
|
I'm not sure if this is related but in various applications I've seen the TimeStamp column being updated automatically by MySQL and it wasn't included in the INSERT or UPDATE statements. That way MySQL was updating TimeStamp automatically, regardless of its format.
But it's good point if you're updating TimeStamp manually or displaying it's values.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
