Hi Comunity,
I have a problem while configuring 'Replication'. My Master Database
is MySql 4.1.8-standard version, and Slave is 5.0.
I want to set Replication between them. Problem here is in MySql
4.1.8-standard version the 'user' table fields are
Host, User, Password, Select_priv, Insert_priv
Hello.
Not enough information to make a conclusion. This could be a bug, say:
http://bugs.mysql.com/bug.php?id=12410
Slawomir Orlowski (CYMPAK) wrote:
hello,
I have mysql-4.1.8 compiled form source working on RH7.2.
I have tried to backup my database with mysqldump
hello,
I have mysql-4.1.8 compiled form source working on RH7.2.
I have tried to backup my database with mysqldump.
mysqldump --opt database_name database_name.sql
mysqldump --lock-tables database_name database_name.sql
mysqldump --skip-opt --lock-tables database_name database_name.sql
Slawomir Orlowski (CYMPAK) wrote:
hello,
I have mysql-4.1.8 compiled form source working on RH7.2.
I have tried to backup my database with mysqldump.
mysqldump --opt database_name database_name.sql
mysqldump --lock-tables database_name database_name.sql
mysqldump --skip-opt --lock-tables
RHEL some day myself.)
Bob Cochran
Shaun T. Erickson wrote:
I'd like to upgrade my RHEL ES v3 u4 server from MySQL 4.1.8 to 4.1.9.
It's using rpms from the MySQL site, and the new ones will be from
there as well.
Assuming I shut down MySQL and any apps that use it, is it as simple
as upgrading
Hello.
You can enable logging on the server. See:
http://dev.mysql.com/doc/mysql/en/log-files.html
You need the error log, query log, slow log. But be careful!
Heavy loaded server can produce a lot of messages and your
files will grow quickly. If you use InnoDB, you can enable
the
I have a mysql server running on WIN-XP (in a critical
health area) and it started to give me that error.
At first, the problem ocurred in a machine and then
started to scatter all over the system. On Saturday I
reset the Server Machine and the problem disapeared.
But today applications started
Hello.
We want only mysql 4.1.8 client version
RPMs with 4.1.8 client programs for Linux on x86, IA64, AMD64 are aviable from:
http://downloads.mysql.com/archives.php?p=mysql-4.1v=4.1.8
But MySQL Server 4.1.9 would be a better choice.
sirisha gnvg [EMAIL PROTECTED] wrote
We want only mysql 4.1.8 client version .How to get only client installed
without server being installed?
Thanking you,
yours sincerely
One thing I left out is that we are running 4.1.8-Max-log not
4.1.8-standard-log
Could that have anything to do with it?
Thanks for any insight,
Frank
On Mon, 17 Jan 2005 15:55:06 -0500, Frank Febbraro
[EMAIL PROTECTED] wrote:
Hey all,
I have setup replication in the past on 4.0.x
into the database.
Does anyone have any experience in dealing with inserting Japanese symbols
in MySQL 4.1 via PHP5?
Thanks again,
- Martin
-Original Message-
From: Daniel BODEA [mailto:[EMAIL PROTECTED]
Sent: 17 January 2005 23:20
To: Martin Gallagher
Subject: Re: MySQL 4.1.8
directory.
-Original Message-
From: Frank Febbraro [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 18, 2005 9:41 AM
To: mysql@lists.mysql.com
Subject: Re: Replication Slave I/O Thread won't start on 4.1.8
One thing I left out is that we are running 4.1.8-Max-log not
4.1.8-standard-log
I believe CREATE VIEW came in with 5.01, not 4.1.x.
PB
sirisha gnvg wrote:
we are working on mysql 4.1.8 and windows XP platform.
This version supports views.We created a view like this
mysqluse sample
mysqlcreate view v1 as select * from sam2;
sam2 is a table
We got an error
errror 1024(42000
- make sure log-bin is enabled on both master and slave (looks like it is not
present in the slave config)
Why is log-bin needed on the slave? I thought the master logs changes
and the slave reads those changes and updates it's copy. Why should
the slave also log changes it is making? There
- make sure log-bin is enabled on both master and slave
(looks like it is not present in the slave config)
Why is log-bin needed on the slave? I thought the master logs changes
and the slave reads those changes and updates it's copy. Why should
the slave also log changes it is making?
: Heikki Tuuri [EMAIL PROTECTED]
Lähetetty: Monday, January 17, 2005 11:11 AM
Aihe: Re: MySQL 4.1.8 InnoDB: data unavailability among different
connections
Thank you all for the hints.
What will be then the best solution to always get the latest data?
- Use commits (e.g. 'COMMIT; SELECT . ) before
] [mailto:[EMAIL PROTECTED]
Sent: 15 January 2005 22:09
To: Martin Gallagher
Cc: mysql@lists.mysql.com
Subject: RE: MySQL 4.1.8 and storing east characters
So its just the Japanese titles which aren't working? The Greek and
Cyrillic looked ok to me. If that's the case then the causes which occur
Hey all,
I have setup replication in the past on 4.0.x servers so I figured I
knew what I was doing...silly me. I reread all of the docs and best I
can tell I followed them sufficiently.
When I start my slave, the SQL Thread starts, but the I/O thread never
starts, and thus the Master Thread
we are working on mysql 4.1.8 and windows XP platform.
This version supports views.We created a view like this
mysqluse sample
mysqlcreate view v1 as select * from sam2;
sam2 is a table
We got an error
errror 1024(42000):you have an error in your sql syntax;
we checked the manual
sirisha gnvg wrote:
we are working on mysql 4.1.8 and windows XP platform.
This version supports views.We created a view like this
mysqluse sample
mysqlcreate view v1 as select * from sam2;
sam2 is a table
We got an error
errror 1024(42000):you have an error in your sql syntax;
we checked
://www.innodb.com/order.php
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: Jose Antonio [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Saturday, January 15, 2005 1:34 AM
Subject: Re: MySQL 4.1.8 InnoDB: data unavailability among
Hi,
Ive recently upgraded to MySQL 4.1.8 for the UTF-8 support.
Ive updated my previous data which was Western European languages, now Id
like to get to grips on more exotic dialects such as Korean, Japanese and deep
East languages such as Greek and Romanian.
The problem is I keep
How are you inserting the data into mysql? LOAD DATA INFILE? Be sure the
client you are using to import the data is using the utf8 character set:
SET CHARACTER SET utf8 or --default-character-set=utf8
The best way to check whether the data was inserted into mysql correctly is to
use the
,
- Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 15 January 2005 20:47
To: mysql@lists.mysql.com
Subject: Re: MySQL 4.1.8 and storing east characters
How are you inserting the data into mysql? LOAD DATA INFILE? Be sure the
client you
2005 20:47
To: mysql@lists.mysql.com
Subject: Re: MySQL 4.1.8 and storing east characters
How are you inserting the data into mysql? LOAD DATA INFILE? Be sure the
client you are using to import the data is using the utf8 character set:
SET CHARACTER SET utf8 or --default-character-set=utf8
Hi!
I am experiencing something weird using MySQL 4.1.8 with InnoDB tables.
I have an application, let's call it A, that is monitoring the data that
is available in the database. The data is inserted in the database by a
different application, let's call it B. The problem is the following
simple answer is transactions. until you issue a commit, or otherwise
specify extra settings in your SQL syntax, other connections do not see
your data.
Jose Antonio wrote:
Hi!
I am experiencing something weird using MySQL 4.1.8 with InnoDB tables.
I have an application, let's call
do not
see your data.
Jose Antonio wrote:
Hi!
I am experiencing something weird using MySQL 4.1.8 with InnoDB tables.
I have an application, let's call it A, that is monitoring the data
that is available in the database. The data is inserted in the
database by a different application, let's call
When I su mysql and run mysqld I get this:
050107 14:09:12 [Warning] Asked for 196608 thread stack, but got 126976
mysqld: Can't create/write to file '/tmp/ib5ArcLz' (Errcode: 13)
050107 14:09:12 InnoDB: Error: unable to create temporary file; errno: 13
050107 14:09:12 [ERROR] Can't init
OK I am running Fedora Core3, Kernel kernel-2.6.9-1.724_FC3 along with
MySQL-server 4.1.8-0.i386.
No matter what I do MySQL the process will not start. This happens to me on
a couple of boxes.
One of the boxes which was upgraded from Fedora Core2 to Core3 does work
with the exact same versions
link to mysql version you use:
[EMAIL PROTECTED] santino]# file /usr/local/mysql
/usr/local/mysql: symbolic link to `mysql-max-4.1.8-pc-linux-i686'
At 14:15 -0500 7-01-2005, Joey wrote:
OK I am running Fedora Core3, Kernel kernel-2.6.9-1.724_FC3 along with
MySQL-server 4.1.8-0.i386.
No matter what I
Hello list and happy new year.
Recently I've install mysql 4.1 on win 2000 with IIS 5 and works
perfect. My problem is that when i'm trying to make a connection with
myodbc (latest release) as localhost I got the following message:
Client does not support authentication protocol requestet by
Have a look at:
http://dev.mysql.com/doc/mysql/en/Old_client.html
Marc.
-Message d'origine-
De : nikos [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 5 janvier 2005 10:09
À : mysql@lists.mysql.com
Objet : MyODBC 3.5.9 and MySQL 4.1.8
Hello list and happy new year.
Recently I've
2005 10:09
À : mysql@lists.mysql.com
Objet : MyODBC 3.5.9 and MySQL 4.1.8
Hello list and happy new year.
Recently I've install mysql 4.1 on win 2000 with IIS
5 and works
perfect. My problem is that when i'm trying to make
a connection with
myodbc (latest release) as localhost I got
To: mysql@lists.mysql.com
Subject: MyODBC 3.5.9 and MySQL 4.1.8
Hello list and happy new year.
Recently I've install mysql 4.1 on win 2000 with IIS 5 and works perfect. My
problem is that when i'm trying to make a connection with myodbc (latest
release) as localhost I got the following message:
Client
4.1.8
Hello list and happy new year.
Recently I've install mysql 4.1 on win 2000 with IIS
5 and works perfect. My
problem is that when i'm trying to make a connection
with myodbc (latest
release) as localhost I got the following message:
Client does not support authentication protocol
, January 06, 2005 12:43 AM
Subject: RE: MyODBC 3.5.9 and MySQL 4.1.8
Tom, this is awesome! It must have been fresh out of
dev because I downloaded 3.51.09 a couple of days ago.
I just downloaded it and it works fine with 4.1
authentication.
Thanks!
--- Tom Crimmins [EMAIL PROTECTED] wrote
It would be nice if phpMyAdmin would kindly note that on their website...
Also, when I run a phpInfo()... it says i have the 3.23.49 could this
be a contributing factor?
On Sat, 1 Jan 2005 15:55:27 +0700, Willy Sudiarto Raharjo
[EMAIL PROTECTED] wrote:
Has anyone had any problems installing
The problem is not with phpmyadmin, the problem is with php. If you install
4.3 of php it will not work with mysql 4.1.8 or any version mysql 4.1 or
5.0. It will only work if you turn on the short passwords option in 4.1.
I've not tried it on 5.0 lately. You can get it installed but it takes
Has anyone had any problems installing phpMyAdmin with the above
configuration? I get an error about the mySql client and
authentication methods? MySQL Error: 1251 : Client does not support
authentication protocol requested by server
Please assist
Happy New Year
Gary
--
MySQL General Mailing
Hello.
At first you should look through all changes from 4.1.1 to 4.1.8 listed
in manual. There are extra steps which required during upgrade in some cases.
I haven't found anything in the documentation that will help me upgrade
mysql from 4.1.1 to 4.1.8. We have several databases
/html; charset=iso-8859-2\n\n;
Everything was working I coud see polish fonts on my web pages and could
save through html FORM-s to the mysql database.
Everything worked just fine.
But because mysql crased one day I decided to upgrade to
mysql-standard-4.1.8 (binnary distribution) (I had to recompile
Hi Vivek, all!
Am Die, 2004-12-28 um 00.23 schrieb Rajan, Vivek K:
Hello-
I am looking for ELF-64 relocatable object file - PA-RISC 2.0 (LP64)
platform binaries for 4.1.8 mysql. Please lemme know where I can
download this from?
Thanx,
Vivek
PS: I downloaded this from the mysql.com
I haven't found anything in the documentation that will help me upgrade
mysql from 4.1.1 to 4.1.8. We have several databases running under
4.1.1. How do they get migrated to run under 4.1.8? How do we
migrate our user data over? Can someone point me toward a FAQ that
might help me
Hello-
I am looking for ELF-64 relocatable object file - PA-RISC 2.0 (LP64)
platform binaries for 4.1.8 mysql. Please lemme know where I can
download this from?
Thanx,
Vivek
PS: I downloaded this from the mysql.com
mysql-standard-4.1.8-hp-hpux11.00-hppa2.0w
ptdh172:vkrajanfile
!
IMHO this the bug in 4.1.8 to create library shared libraries
without .so suffix.
After this any programs linked with static libraries not dynamic,
because of convention lib*.so.[0-9] in shared libraries names.
ldconfig doesn't see new libraries at all too.
This bug in 4.1.8
4.1.7 compiled
SQL
Hello, All!
IMHO this the bug in 4.1.8 to create library shared libraries without .so
suffix.
After this any programs linked with static libraries not dynamic,
because of convention lib*.so.[0-9] in shared libraries names.
ldconfig doesn't see new libraries at all too.
This bug in 4.1.8
Yes, this has been reported on this list a couple times already.
Really baffling how this one made it out of QA.
Josh
On Thu, 23 Dec 2004 21:43:27 +0200 (EET)
Andrey Kotrekhov [EMAIL PROTECTED] wrote:
SQL
Hello, All!
IMHO this the bug in 4.1.8 to create library shared libraries
Hi!
InnoDB is the MySQL table type that supports FOREIGN KEY constraints,
row-level locking, Oracle-style consistent, non-locking SELECTs, multiple
tablespaces, and a non-free online hot backup tool.
Release 4.1.8 is mainly a bugfix release. There was a critical bug
associated
Hi,
MySQL 4.1.8, a new version of the popular Open Source/Free Software
Database Management System has been released. It is now available in
source and binary form for a number of platforms from our download pages
at http://dev.mysql.com/downloads/ and mirror sites.
Note that not all mirror
Does 4.1.8 address any of the issues I am reading about in 4.1.7? Are all
of these issues valid or are you finding that its Lazy coding?
Thanks
Donny Lairson
President
http://www.gunmuse.com
469 228 2183
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
I think a lot of it has to do with the fact that 4.1 is now production and a
lot more people are now using it then before. So you are bound to have new
bugs crop up, or in some cases people think they are bugs and they just
haven't read the manual. You can see what's already been fixed for 4.1.8
52 matches
Mail list logo
