Reindl,
I am sorry, in my original post, I forgot to mention that the OLD box and
the NEW box are the same physical machine. I need to be able to save all
data into files on a memstick or portable disc and restore them to the newly
staged machine (with the new version of mysql).
-Grant
--
a newer version.
* the YEAR(2) data type is no longer supported.
* pre 4.1 passwords - If you are upgrading from version 5.1 or older,
you will need to update their hashes or configure 5.6 to recognize the
older hashes as valid. The user authentication system in 5.6 is more
advanced than
Shawn all,
Thank you for taking to time to reply.
So, to be clear, what I understand from your post is that replacing the
new build's grant/system tables with the archived ones from the previous
version, generally works fine, upgrade issues not withstanding. This is the
answer I
Am 26.12.2014 um 20:52 schrieb Grant Peel:
Shawn all,
Thank you for taking to time to reply.
So, to be clear, what I understand from your post is that replacing the
new build's grant/system tables with the archived ones from the previous
version, generally works fine, upgrade issues not
Hi all,
I was wondering if anyone knows of a concise tutorial on how to upgrade (by
moving from one box (old) to another box (new) mysql in a virtual
environment (many mysql users, many databases).
Example:
Mysql 5.x setup on freebsd 8.x (x86/32b), call this box A.
Want to move to
Am 25.12.2014 um 16:01 schrieb Grant Peel:
I was wondering if anyone knows of a concise tutorial on how to upgrade (by
moving from one box (old) to another box (new) mysql in a virtual
environment (many mysql users, many databases).
Mysql 5.x setup on freebsd 8.x (x86/32b), call this box A.
Am 20.02.2013 18:26, schrieb Mike Franon:
So I did a full mysqldump over the weekend for a second time and this
time it is 220GB, no clue what happened last time, I should have
realized looking at the file size something was wrong, but since I got
no errors did not think about it, and this
So I did a full mysqldump over the weekend for a second time and this
time it is 220GB, no clue what happened last time, I should have
realized looking at the file size something was wrong, but since I got
no errors did not think about it, and this time I timed it, took 7
hours to do a complete
I am pretty sure I did, and when I did I got the following errors:
Error: Table Upgrade Required, Please dump/reload to fix it
I got that on 10 tables, and also got the following:
Warning: Triggers for table ' have no creation context.
I think it has to do with no triggers.
I know hen I
OK I got it to work.
I dumped the tables that it was complaining about first, and then
dumped the triggers.
I then uninstalled anything to do with mysql, and installed 5.1
Then imported the tables and triggers, and and able to run
mysql_upgrade without any errors.
This is all without using a
fine and much faster and probably safer too :-)
a backup with rsync is faster as dump/import and
can be done with minimize downtime by use it
twice, the first time hot-backup with running
server and the second time after stop server
to get the diffs
doing rsync - stop - rsync - start in a script
going form 5.1 - to 5.5 was easy, I did not have to dump any tabels or
triggers, just upgraded binary, ran mysql_upgrade and worked in no
time.
Thanks everyone for the help!
On Wed, Feb 20, 2013 at 2:33 PM, Reindl Harald h.rei...@thelounge.net wrote:
fine and much faster and probably safer too
surely
* use mysql_upgrade -u root -p after EACH update
* upgrade regulary
we went from MySQL 3.x to 5.5.30 until know without
any dump and here are around 5000 tables
Am 19.02.2013 22:12, schrieb Divesh Kamra:
Is there any better way for grade MySQL version without taking backup with
Use replication as your fail over and why not percona's xtrabackup or lvm type
backup if you need a backup?
Sabika
On Feb 19, 2013, at 1:20 PM, Reindl Harald h.rei...@thelounge.net wrote:
surely
* use mysql_upgrade -u root -p after EACH update
* upgrade regulary
we went from MySQL
Hi Reindi
Thanks for solution .
Can u share complete steps ?
R's
DK
On 20-Feb-2013, at 2:50, Reindl Harald h.rei...@thelounge.net wrote:
surely
* use mysql_upgrade -u root -p after EACH update
* upgrade regulary
we went from MySQL 3.x to 5.5.30 until know without
any dump
Am 19.02.2013 23:53, schrieb Divesh Kamra:
Hi Reindi
Thanks for solution .
Can u share complete steps ?
which steps?
* update
* call mysql_upgrade -u root -p
in doubt mysqlcheck -h localhost --check-upgrade --all-databases --auto-repair
--user=root -p
and if you do
Hi all
Is there any better way for grade MySQL version without taking backup with
mysqldump
Or if there any tool for this
R's
DK
On 16-Feb-2013, at 16:07, Reindl Harald h.rei...@thelounge.net wrote:
Am 16.02.2013 09:42, schrieb Manuel Arostegui:
2013/2/15 Reindl Harald
2013/2/15 Reindl Harald h.rei...@thelounge.net
our database is 400 GB, mysqldump is 600MB was not a typo and you
honestly believed that you can import this dump to somewhat?
WTF - as admin you should be able to see if the things in front
of you are theoretically possible before your start
Am 16.02.2013 09:42, schrieb Manuel Arostegui:
2013/2/15 Reindl Harald h.rei...@thelounge.net
mailto:h.rei...@thelounge.net
our database is 400 GB, mysqldump is 600MB was not a typo and you
honestly believed that you can import this dump to somewhat?
WTF - as admin you
PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few instances where it was an issue
at my last job. It basically involved multi-table deletes
with precedence of commajoin vs
explicit
JOIN.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400 GB, mysqldump is 600MB file, about 30 minutes into the
restore get this error on one table on an insert:
ERROR 1064 (42000) at line 1388: You have
Am 15.02.2013 22:55, schrieb Mike Franon:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400 GB, mysqldump is 600MB file, about 30 minutes into the
restore get this error on one table
at the
offending line.
Keith
On Feb 15, 2013 3:55 PM, Mike Franon kongfra...@gmail.com wrote:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400 GB, mysqldump is 600MB file, about 30 minutes
having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400 GB, mysqldump is 600MB file, about 30 minutes into the
restore get this error on one table on an insert:
ERROR 1064 (42000) at line 1388: You have
just edit it with something like vi and look at the
offending line.
Keith
On Feb 15, 2013 3:55 PM, Mike Franon kongfra...@gmail.com wrote:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400
a gig I would just edit it with something like vi and look at
the
offending line.
Keith
On Feb 15, 2013 3:55 PM, Mike Franon kongfra...@gmail.com wrote:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep
.
Keith
On Feb 15, 2013 3:55 PM, Mike Franon kongfra...@gmail.com wrote:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400 GB, mysqldump is 600MB file, about 30 minutes into the
restore get
PM, Mike Franon kongfra...@gmail.com wrote:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400 GB, mysqldump is 600MB file, about 30 minutes into the
restore get this error on one table
.
Keith
On Feb 15, 2013 3:55 PM, Mike Franon kongfra...@gmail.com
mailto:kongfra...@gmail.com wrote:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database
server running for several days before
upgrading the rest of machines to 5.6. If possible, I would do some stress
tests or benchmarking to make sure it performs as you expect.
Manuel.
Great thanks for the info, I guess the best way to do this is take a
spare server, set it up with our standard setup, and then start the
upgrade as you said 5.0 - 5.1 - 5.5, test and then upgrade to 5.6
and test.
On Thu, Feb 14, 2013 at 4:22 PM, Akshay Suryavanshi
Mike,
5.6 is GA now, so its stable release. Also you should not jump to 5.6
directly, atleast from 5.0.
There are many bug fixes and changes in 5.1, so you should consider this
way.
5.0--5.1--5.5 (all slaves first, and then the master)
And further 5.5 -- 5.6 (again all slaves first and then
the way to 5.6? Maybe. You need to do a lot of shakedown
anyway.
-Original Message-
From: Mihail Manolov [mailto:mihail.mano...@liquidation.com]
Sent: Thursday, February 14, 2013 2:22 PM
To: Mike Franon
Cc: Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql
Singer, do you have some examples?
-Original Message-
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 2:59 PM
To: Mihail Manolov
Cc: Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
...@liquidation.com]
Sent: Thursday, February 14, 2013 3:30 PM
To: Rick James
Cc: Singer Wang; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
The ones that didn't work for me required table rearrangement in the
query. MySQL 5.5 was very
, the other with precedence of commajoin vs explicit
JOIN.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very
To: Mihail Manolov
Cc: Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
There are queries that works with 5.1/5.0 that do not work with 5.5, I
would test extensively..
S
On Thu, Feb 14, 2013 at 5:22 PM, Mihail Manolov
You could jump from 5.0 directly to 5.5 and skip 5.1. I have without any
issues. There are some configuration file change, which you may want to
consider checking. I definitely recommend upgrading your development servers
for an extensive testing. Some queries _may_ run slower or not work
configuration file change, which you may want to
consider checking. I definitely recommend upgrading your development
servers for an extensive testing. Some queries _may_ run slower or not work
at all and you may have to rearrange how you join tables in your queries.
The upgrade from 5.5 to 5.6 should me
]
Sent: Thursday, February 14, 2013 2:59 PM
To: Mihail Manolov
Cc: Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
There are queries that works with 5.1/5.0 that do not work with 5.5, I
would test extensively..
S
On Thu, Feb
I've posted a similar post in the past -- but there I was mucking around
with blank index files and frm files to fool myisamchk into repairing a
table.
But now I think I've come across a much better and more efficient way to do
a REPAIR Table in order to upgrade my database tables from Mysql
Sorry...
One small correction to my above post..
'FLUSH TABLES' should be issued between steps 8 and 9.
My 200+ million record table completed in 71 minutes.
-Hank
mysql; query;
Hi All
Sorry for all my posts today but this one client is keeping me
busy.
the version of MySQL installed on the ubuntu server is
5.0.51a-3ubuntu5.8-log as this was the latest one available in the
repository.
We will need to upgrade this to version 5.1.53.
Am
That would work, yes.
You could also try to upgrade in place - the upgrade scripts *should* take
care of everything between those versions, I think. Make sure you have a
backup in any case :-)
On Mon, Nov 22, 2010 at 12:57 PM, Machiel Richards machi...@rdc.co.zawrote:
Hi All
Sorry
...@lists.mysql.com%3e
*Subject*: Re: Upgrading of mysql database
*Date*: Mon, 22 Nov 2010 15:25:44 +0100
That would work, yes.
You could also try to upgrade in place - the upgrade scripts *should* take
care of everything between those versions, I think. Make sure you have a
backup in any case
How would I do an inplace upgrade?
-Original Message-
From: Johan De Meersman vegiv...@tuxera.be
To: Machiel Richards machi...@rdc.co.za
Cc: mysql mailing list mysql@lists.mysql.com
Subject: Re: Upgrading of mysql database
Date: Mon, 22 Nov 2010 15:25:44 +0100
That would work, yes.
You
Hi all, I was reading a few of the notes on this forum from a few months back
and it seems that ONE WAY of upgrading from 4.x to 5.X with MyISAM only
databases is to copy the actual data folder from the 4.X version to a temp
place, then remove 4.x from the OS, install 5.X and then just put
On Mon, August 16, 2010 07:26, Nunzio Daveri wrote:
Hi all, I
was reading a few of the notes on this forum from a few months
back
and it seems that ONE WAY of upgrading from 4.x to 5.X with
MyISAM only
databases is to copy the actual data folder from the
4.X version to a temp
place
wrote:
On Mon, August 16, 2010 07:26, Nunzio Daveri wrote:
Hi all, I
was reading a few of the notes on this forum from a few months
back
and it seems that ONE WAY of upgrading from 4.x to 5.X with
MyISAM only
databases is to copy the actual data folder from the
4.X version to a temp
the data is in MyISAM, zero InnoDB :-)
Thanks again for the advice :-)
Nunzio
From: Keith Murphy bmur...@paragon-cs.com
To: Nunzio Daveri nunziodav...@yahoo.com
Sent: Mon, August 16, 2010 9:42:07 AM
Subject: Re: Is upgrading from 4.X to 5.X really that easy
AM
Subject: Re: Is upgrading from 4.X to 5.X really that easy?
No, that would be a huge mistake. There are subtle differences between the
two
versions. For example, check up on DECIMAL. Also, 5.0 and 5.1 have numerous
new
reserved words.
You need to think about this carefully before you do
break something during the dump and can revert within mins back to the
4.x version?
Still don't know why I should do a mysql dump from 4.1.X to 5.0.x and then
upgrade 5.0.x to 5.1.48 esp. if I am doing nothing more than a mysql dump and
not upgrading in place ;-)
TIA...
Nunzio
Hi,
I am looking at upgrading my servers Debian version from Etch to Lenny, and
in doing that, I think it will upgrade MySQL from 5.0.32 to the lenny
version, which is 5.0.53 (I think).
I have also been thinking about using the 'dotdeb' packages, which will
upgrade it even further to 5.1.47. I
On Wed, Jun 23, 2010 at 6:33 AM, Steven Staples sstap...@mnsi.net wrote:
Hi,
I am looking at upgrading my servers Debian version from Etch to Lenny, and
in doing that, I think it will upgrade MySQL from 5.0.32 to the lenny
version, which is 5.0.53 (I think).
I have also been thinking about
The issue is that in theory this should work given the facts announced
by MySQL regarding binary logging and replication.
I can certainly do it the way you propose, but to my mind I should also
be able to do it using the fact that both machines are fully synced and
hence at
that point I should
On 1/13/10 2:28 PM, Lawrence Sorrillo sorri...@jlab.org wrote:
The issue is that in theory this should work given the facts announced
by MySQL regarding binary logging and replication.
I can certainly do it the way you propose, but to my mind I should also
be able to do it using the fact that
On Jan 13, 2010, at 1:28 PM, Lawrence Sorrillo wrote:
The issue is that in theory this should work given the facts announced by
MySQL regarding binary logging and replication.
I can certainly do it the way you propose, but to my mind I should also be
able to do it using the fact that both
Hi:
I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1.
I want to so something like follows:
1. Stop all write access to the master server.
2. Ensure that replication on the slave is caught up to the last change
on the master.
3. stop binary logging on the master.
4.
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master, upgrade it, restart it, let the slave catch up.
?
On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote:
Hi:
I want to upgrade a master and slave server from mysql 4.1 to mysql
: upgrading mysql
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master, upgrade it, restart it, let the slave catch up.
?
On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote:
Hi:
I want to upgrade a master and slave server from mysql
This is two upgrades done in sequence(the reload takes about three hours
per machine) . I can do what I am proposing in parallel.
Do you see it as problematic?
~Lawrence
Tom Worster wrote:
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master,
Lawrence Sorrillo wrote:
Hi:
I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1.
I want to so something like follows:
1. Stop all write access to the master server.
ok
2. Ensure that replication on the slave is caught up to the last change
on the master.
why? You
Hi:
I want to ensure that right after the reload that the same data is
present in both the master and the slave. They are in perfect sync. Then
I think its safe to consider starting binary logging and replication
etc. And after these are started, changes can start?
And in setting up
there it should start
reading the binary logs and committing changes properly.
Is this correct?
You're upgrading to MySQL 5.1, for which several of those options no longer
have any effect. Better to use CHANGE MASTER. See:
http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html
http
Frankly, I didn't entirely understand what you were proposing. I got lost
around step 6.
Is the issue total time for the procedure or service downtime?
On 1/12/10 12:58 PM, Lawrence Sorrillo sorri...@jlab.org wrote:
This is two upgrades done in sequence(the reload takes about three hours
per
Hi,
The step 6 in simple terms is
Here we need to build two server ( both master and slave ). Instead of
building two server as it takes double the time of building in one server.
After building an server, make a copy of the first server files at OS level
and copy it to the server and start the
Hi!
I don't do DBA work, so my info may be incomplete:
monem mysql wrote:
Hello
I have to upgrade many mysql databases from mysql 4 and 4.1 to 5.4 with a
large size 2.7 TB
[[...]]
The official method takes too much time. But I've read that we can use '*dump
and reload'* to
Hello
I have to upgrade many mysql databases from mysql 4 and 4.1 to 5.4 with a
large size 2.7 TB
All tables use the MyISAM engine.
I have to make that update on live system with minimal down time possible.
The official method takes too much time. But I’ve read that we can use ‘*dump
and
Subject: upgrading from 4.1 to 5.4
Hello
I have to upgrade many mysql databases from mysql 4 and 4.1 to 5.4 with a
large size 2.7 TB
All tables use the MyISAM engine.
I have to make that update on live system with minimal down time possible.
The official method takes too much time. But I've
Hi all,
I've got a quite large database (23G) that is running on a 5.0.32
version of MySQL. I really want to upgrade out of 5.0.32 to the
latest version of 5.1 (or even 5.4) but a straight mysql_upgrade of
the database takes long enough that I'd have serious down-time issues
(last time I
David Harrison wrote:
Hi all,
I've got a quite large database (23G) that is running on a 5.0.32
version of MySQL. I really want to upgrade out of 5.0.32 to the
latest version of 5.1 (or even 5.4) but a straight mysql_upgrade of
the database takes long enough that I'd have serious
On Fri, Aug 28, 2009 at 9:18 AM, Shawn Green shawn.gr...@sun.com wrote:
Hank wrote:
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the mysqlcheck --check-upgrade --auto-repair
command,
and on one of my MYISAM tables, it's taking
Hank wrote:
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the mysqlcheck --check-upgrade --auto-repair command,
and on one of my MYISAM tables, it's taking forever to upgrade the table.
It has about 114 million rows, and I'm guessing
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the mysqlcheck --check-upgrade --auto-repair command,
and on one of my MYISAM tables, it's taking forever to upgrade the table.
It has about 114 million rows, and I'm guessing it needs
got to be a better way?
I couldn't figure out how to get the new version 5.1 to see the file system
(containing the database) that was in use by 5.0. I looked at all the
documents and nowhere (or at least I couldn't see it) does it talk about
upgrading the database. When you install the new
Trying to upgrade from 5.0.37 to 5.1.32, These are the steps I have taken:
1. Took a dump of the our production database using mysqldump.
2. Downloaded the binary version for i86 Linux and placed it on a Slackware 12
server.
3. Foolishly ran mysql_upgrade against the data
users, etc. There's got to be a
better way?
I couldn't figure out how to get the new version 5.1 to see the file system
(containing the database) that was in use by 5.0. I looked at all the documents
and nowhere (or at least I couldn't see it) does it talk about upgrading the
database. When you
,
and quite honestly, if it ain't broke don't fix it is a good mantra of
mine... but I need to move on now as I have received an sql file that
is v5 compatible but not v4 compatible.
Once I have it up and running I'll be fine, it's just that I am
nervous about upgrading and consequently
compatible but not v4 compatible.
Once I have it up and running I'll be fine, it's just that I am
nervous about upgrading and consequently breaking it, and at that
point, I'll be struggling to put it right.
Any advice on how I can best do this / best practices etc will be very
much
broke don't fix it is a good
mantra of mine... but I need to move on now as I have received an
sql file that is v5 compatible but not v4 compatible.
mysql@lists.mysql.com
Once I have it up and running I'll be fine, it's just that I am
nervous about upgrading and consequently breaking
received an
sql file that is v5 compatible but not v4 compatible.
mysql@lists.mysql.com
Once I have it up and running I'll be fine, it's just that I am
nervous about upgrading and consequently breaking it, and at that
point, I'll be struggling to put it right.
Any advice on how I can best do
Does anyone have experience with upgrading large databases (~500GB each)
from MySQL 4.1 to 5.0? The tables are in InnoDB format. We are using the
Community version.
I've read that it's recommended that you use mysqldump and then restore,
but this is not possible for us, as we cannot have our
and the slave becomes the master.
Very simple in theory, a bit more complicated in practice.
Brent Baisley
Systems Architect
On Apr 23, 2008, at 2:28 PM, Paul Choi wrote:
Does anyone have experience with upgrading large databases (~500GB
each)
from MySQL 4.1 to 5.0? The tables are in InnoDB format. We
Has anyone upgraded MySQL 4.0 to 5.0 on a Mac running Mac OS X
Panther, 10.3.9 Sever with Lasso 8.5.4? I'm debating whether to just
upgrade to MySQL to 5.0 or jump to Apples Leopard Server.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
Hi Gurus,
I have mysql4.x installed on REHL4.
Can anybody let me know how to upgrade it to 5.1.
Also please tell me where can i get mysql5.1 enterprise edition.
Thanks in advance
Siva
Hi,
Take backup of the existing data before upgrading for safety. There is RHEL 4
specific rpm binary is existing in the downloading section. After installing
run the required tools comes with mysql.
Before upgrading with existing datas read the documentation carefully.
http
Hi !
perl pra schrieb:
[[...]]
Also please tell me where can i get mysql5.1 enterprise edition.
5.1 is currently labeled rc (current version is 5.1.22-rc), so there
is no enterprise edition yet.
When there will be one, it will be for paying customers, and they have
got (or will receive) the
to be the recommended way of upgrading a MySQL 3 installation. I then
went on to recompile PHP 4.4.7, which worked fine. But my PHP
installation is still using libmysqlclient.so.10, which does not play
100% correctly with the current MySQL 5 server. I'd need it to use
libmysqlclient.so.15. Apparently /usr
Is it possible to log information to the general log file only for a specific
database?
We are currently running MySQL 4.0.15. We are planning on moving to a new
server so and will upgrade MySQL. What is the latest most stable version that
is recommended?
Thanks for any information.
--
I don't think there is any way to lock down the general log to a
single database.. perhaps if you tell us what you are trying to
accomplish, we might be able to propose something..
As of today, 5.0.45 is the recommended install version.
http://dev.mysql.com/downloads/mysql/5.0.html
-
Since we upgraded from MySQL 4.0 to 5.0 (under OpenBSD 4.1 amd64) the
following command:
select count(*) as total from products_description pd, products p left
join manufacturers m on p.manufacturers_id = m.manufacturers_id,
products_to_categories p2c left join specials s on p.products_id =
Try not mixing left join and comma-joins, and use an INNER JOIN keyword
between m.manufacturers_id, products_to_categories
Baron
Federico Giannici wrote:
Since we upgraded from MySQL 4.0 to 5.0 (under OpenBSD 4.1 amd64) the
following command:
select count(*) as total from
Hi Frederico,
the precedence between the comma-operator and JOIN changed
with 5.0.12.
See http://dev.mysql.com/doc/refman/5.0/en/join.html
Excerpt from that article:
Previously, the comma operator (,) and JOIN both had the same
precedence, so the join expression t1, t2 JOIN t3 was interpreted as
the mysql_fix_privilege_tables script which gave me some warnings, but
seemed OK. The test forum and databases started up fine.
Soon, I'll upgrade to 4.1 and then later to version 5 of the mysql server.
My question is: When upgrading mysql-server and running suggested/included
update scripts etc
Hello,
I'm having trouble copying a database from MySQL 4.1.22 to 5.1.19-
beta. Both are FreeBSD i386-based machines. I have run the
following commands:
mysqlcheck --check-upgrade --all-databases --auto-repair
mysql_fix_privilege_tables
Both executed with no problems. (mysqlcheck
Seth Seeger wrote:
Hello,
I'm having trouble copying a database from MySQL 4.1.22 to 5.1.19-
beta. Both are FreeBSD i386-based machines. I have run the following
commands:
mysqlcheck --check-upgrade --all-databases --auto-repair
mysql_fix_privilege_tables
Both executed with no problems.
On Jun 21, 2007, at 12:21 PM, Gerald L. Clark wrote:
Seth Seeger wrote:
Hello,
I'm having trouble copying a database from MySQL 4.1.22 to 5.1.19-
beta. Both are FreeBSD i386-based machines. I have run the
following commands:
mysqlcheck --check-upgrade --all-databases --auto-repair
Hi Seth -
I believe MySQL's official position is that you should always dump-and-load
the data when upgrading major or minor versions (4.0 to 4.1, 4.1 to 5.0,
etc.)
I've done it both ways (dump-load and just moving table files) and have
never had a problem with either, even when moving files
Hi! I would like to upgrade the database of my organisation from
mysql4.0.22 from 4.1. We use Debian.
I've read info in the manual, but i don't have things clear.
We process data of DB with scripts, and I'm annoyed because the change
of format of timestamp, is there any command in 4.1 to obtain
1 - 100 of 469 matches
Mail list logo
