Review your join type.
From: ext Gavin Towey [gto...@ffn.com]
Sent: 16 August 2010 19:36
To: Victor Subervi; mysql@lists.mysql.com
Subject: RE: Join Problem
What do you mean by "not working?" What results do you get?
-Original Message-
From: Victo
What do you mean by "not working?" What results do you get?
-Original Message-
From: Victor Subervi [mailto:victorsube...@gmail.com]
Sent: Monday, August 16, 2010 6:59 AM
To: mysql@lists.mysql.com
Subject: Join Problem
Hi;
I have this code:
select f.id from Flights f join Planes p where
Thanks Keith :-) Last question, do you think it's ok for me to do a sqldump on
4.1.22 at say 3 am on sun, then import to 5.1.48 at 4 am and then just edit
etc/hosts and have the web servers now point to 5.1?
This should work without any problems right? Plus I have the original 4.x in
case I b
I would really recommend that you have a second server set up running MySQL
5.0. Otherwise the complexity is going to drive you crazy. Either way you
are going to have to get a backup of the master (4.1) server somehow. I am
curious. If you can't take an hour or so take a mysqldump of the server h
Thanks William and Keith. So how to have min down time since this is a stand
alone mysql 4.1.22 box? Are you saying install 5.X on the same box (port
3307),
then replicate the data as it comes into 4.x to 5.x and when it is all sync'd
up
then turn 4.x off, remove it and have 5.x responding o
MySQL rightly says you should dump and reload. As William said, you should
read the release notes for every release between your current release and
the target release.
I have done this several times. I am currently planning a migration from
4.1.22 to 5.1.49 with a brief stop at 5.0 along the way.
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, the
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 the 4
Hi;
I have this code:
select f.id from Flights f join Planes p where f.plane_id=p.id and
p.in_service=1
mysql> describe Flights;
+-+---+--+-+-++
| Field | Type | Null | Key | Default | Extra |
+-+-
>> 1. Make sure it works
Change this to
1. Make sure it works efficiently and is correctly configured!
Meaning - Just because it works now doesn't mean its going to work when you
put the system live and 2000 users hit the system ;) Don't just accept the
defaults in the sample my.cnf/my.ini files,
1. Make sure it works
2. Make sure it's secure
3. Make sure you have backups
On Mon, Aug 16, 2010 at 7:58 AM, Kranthi wrote:
> Hi all,
>
> Please send sample mysql best practice document.
>
>
>
> Thanks & Regards,
>
> Kranthi kiran
>
>
>
>
--
Bier met grenadyn
Is als mosterd by de
Ryan,, all:
Ryan Chan wrote:
> According to this document:
> http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html
>
> It said MySQL support UTF-8 using one to three bytes per character.
>
> But I have created a test table:
>
> -- create table test ( c char(5) ) default charset =utf8;
>
Ryan Chan wrote:
> According to this document:
> http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html
>
> It said MySQL support UTF-8 using one to three bytes per character.
>
> But I have created a test table:
>
> -- create table test ( c char(5) ) default charset =utf8;
>
> >From the table
13 matches
Mail list logo
