Re: Mysql 4.0 always executes case insensitive queries

[Shen139]

You should use:
SELECT username FROM workflow.user WHERE username LIKE BINARY 'NicO'  LIMIT
1;

reference:
http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html

On 12/12/05, Nico Sabbi <[EMAIL PROTECTED] > wrote:
>
> Hi,
> my mysql always executes case insensitive queries:
>
>
> SELECT username FROM workflow.user WHERE username = 'NicO'  LIMIT 1;
> +--+
> | username |
> +--+
> | nico |
> +--+
> 1 row in set (0.01 sec)
>
>
>
> that field is of varchar(255) type.
>
> I don't understand the reason for this behavior.
> What should I check?
>
Thanks,
>
> Nico
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
>
>


--

http://www.openwebspider.org
http://www.eviltime.com

Re: Mysql 4.0 always executes case insensitive queries

[Wolfram Kraus]

Nico Sabbi wrote:

Hi,
my mysql always executes case insensitive queries:


SELECT username FROM workflow.user WHERE username = 'NicO'  LIMIT 1;
+--+
| username |
+--+
| nico |
+--+
1 row in set (0.01 sec)



that field is of varchar(255) type.

I don't understand the reason for this behavior.
What should I check?

Thanks,

Nico


You need the binary function:

http://dev.mysql.com/doc/refman/4.1/en/cast-functions.html

HTH,
Wolfram


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

[AmirBehzad Eslami]

Mohsen wrote:
  
  > But himself solved his problem.
  > with : mysql_query("SET NAMES utf8");
  > Even 4.0.x
  
  Wrong. 
  
  I decided to prepare two different versions for my software:
  - A MySQL 4.0-friendly version using Romanizing method (Hats off to you, 
Ehsan)
  - A MySQL 4.1-compatible version.
  
  The code you mentioned belongs to the 2nd version.
  
  " SET NAMES indicates what is in the SQL statements that the client  sends. 
Thus, SET NAMES 'cp1251' tells the server “future incoming  messages from this 
client are in character set cp1251.” It also  specifies the character set for 
results that the server sends back to  the client. (For example, it indicates 
what character set column values  are if you use a SELECT statement.) "
  
  MySQL Manual 4.1 -> 10.3.6. Connection Character Sets and Collations.
  
  Kind Regards,
  Behzad
  



-
 Yahoo! Music Unlimited - Access over 1 million songs. Try it free.

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

[Alec . Cawley]

AmirBehzad Eslami <[EMAIL PROTECTED]> wrote on 24/11/2005 18:36:25:

> On 24/11/2005, Alec worte:
> 
>   > I think this is your problem: MySQL does not properly support 
Unicode 
>   > until version 4.1. I am successfully using FullText with MySQL 
> 4.1 to sort 
>   > UTF-8 encoded Japanese text. I see no reason why it should not work 
for 
>   > Arabic - if you upgrade.
> 
>   Dear Alec,
>   Thank you for your prompt reply.
> 
>   You're right. That's my problem. I admit it.
> 
>   But I'm really unable to solve this by upgrading.
>   Many of the Hosting Companies, which I use their services [even 
> the HostRocket.com] still use MySQL 4.0 !!!

Googling for  gives a number of companies offering 
MySQL 4.1 and PHP 5. Obviously I cannot comment on their competence.

> 
>   1) Would you recommend any hosting company with PHP 5 and MySQL 4.1 
support?
> 
>   2) What about if my client only use MySQL 4.0 for his reasons. In 
> this  case, I really can't use FULL-TEXT search? There is no any 
solution?

No. It is inherent in the Fulltext mechanism that the text indexing engine 
knows which bytes represent indexable characters and which separators. 
Before 4.1, Fulltext was 8-bit only - end of story.

Alec


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

[AmirBehzad Eslami]

On 24/11/2005, Alec worte:
  
  > I think this is your problem: MySQL does not properly support Unicode 
  > until version 4.1. I am successfully using FullText with MySQL 4.1 to sort 
  > UTF-8 encoded Japanese text. I see no reason why it should not work for 
  > Arabic - if you upgrade.
  
  Dear Alec,
  Thank you for your prompt reply.
  
  You're right. That's my problem. I admit it.
  
  But I'm really unable to solve this by upgrading.
  Many of the Hosting Companies, which I use their services [even the 
HostRocket.com] still use MySQL 4.0 !!!
  
  1) Would you recommand any hosting company with PHP 5 and MySQL 4.1 support?
  
  2) What about if my client only use MySQL 4.0 for his reasons. In this  case, 
I really can't use FULL-TEXT search? There is no any solution?
  
  Once again, thank you for your reply.
  Behzad



-
 Yahoo! Music Unlimited - Access over 1 million songs. Try it free.

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

[Alec . Cawley]

AmirBehzad Eslami <[EMAIL PROTECTED]> wrote on 24/11/2005 17:48:29:

> Dear list,
> 
>   I'm considering programming a simple "Search Engine" for a website,
>   to find Arabic/Persian data within a MySQL database.
>   This database contains a huge amount of data, encoded with 
Unicode(UTF-8). 
> 
> 
>   The big deal is to ** reduce the response time ** to end-users.
> 
>   My first solution is to create an Index and use the "FULL-TEXT 
> Searching" method.
> 
>   Luckily, MySQL's provides FULL-TEXT Indexing support in MyISAM tables.
>   But unfortunately, it doesn't support multi-byte charsets (e.g. 
> Unicode). [1]
>   Technically, MySQL creates Indexes over words.
>   A "word'' is any sequence of characters consisting of letters and 
> numbers [2].
> 
>   Assuming this, I tried to save the records as Unicode Character 
> References (&#;), but the search failed again :-(
> 
>   Any suggestion?
>   I appreciate any solution to solve this problem.
> 
>   Thanks in Advance,
>   Behzad
> 
> 
>   [1] MySQL Manual -> 6.8.3 Full-text Search TODO
>   [2] MySQL Manual -> 6.8 MySQL Full-text Search
> 
> 
>   P.S.

*** 
>   I use MySQL 4.0
***

I think this is your problem: MySQL does not properly support Unicode 
until version 4.1. I am successfully using FullText with MySQL 4.1 to sort 
UTF-8 encoded Japanese text. I see no reason why it should not work for 
Arabic - if you upgrade.

Alec



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Mysql 4.0 cpu usage

[James Sherwood]

I have solved this problem, I was missing a slash in the path to the data
directory

Thanks,
James


- Original Message - 
From: "Gleb Paharenko" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, October 26, 2005 4:41 AM
Subject: Re: Mysql 4.0 cpu usage


> Hello.
>
> Are you able to connect to the server and found the states of its
> threads with SHOW PROCESSLIST statement?
>
>
> > Mysql 4.1 and 5 will NOT seem to play nice with french characters so I
> have tried to
> > revert back to 4.0.
> >
> > I am trying to install 4.0 on a Win2003 Dell PowerEdge 2850 and when I
> run the
> > service it uses a constant 25%cpu and seems locked up.  I cannot even
> stop the service I
> > have to end the process in the task manager. Any ideas?
>
> James Sherwood wrote:
>
>
> -- 
> For technical support contracts, goto https://order.mysql.com/?ref=ensita
> This email is sponsored by Ensita.NET http://www.ensita.net/
>__  ___ ___   __
>   /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
>  / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
> /_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
><___/   www.mysql.com
>
>
>
>
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
>
>



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Mysql 4.0 cpu usage

[Gleb Paharenko]

Hello.



Are you able to connect to the server and found the states of its

threads with SHOW PROCESSLIST statement?





> Mysql 4.1 and 5 will NOT seem to play nice with french characters so I

have tried to

> revert back to 4.0.

>

> I am trying to install 4.0 on a Win2003 Dell PowerEdge 2850 and when I

run the

> service it uses a constant 25%cpu and seems locked up.  I cannot even

stop the service I

> have to end the process in the task manager. Any ideas?



James Sherwood wrote:



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Mysql 4.0 cpu usage

[Jasper Bryant-Greene]

On Tue, 2005-10-25 at 15:39 -0300, James Sherwood wrote:
> Mysql 4.1 and 5 will NOT seem to play nice with french characters so I have 
> tried to revert back to 4.0.
> 
> I am trying to install 4.0 on a Win2003 Dell PowerEdge 2850 and when I run 
> the service it uses a constant 25%cpu and seems locked up.  I cannot even 
> stop the service I have to end the process in the task manager. Any ideas?

Logs?

-- 
Jasper Bryant-Greene
General Manager
Album Limited

e: [EMAIL PROTECTED]
w: http://www.album.co.nz/
p: 0800 4 ALBUM (0800 425 286) or +64 21 232 3303
a: PO Box 579, Christchurch 8015, New Zealand


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: mysql 4.0 to 4.1 migration and charset problems

[Gleb Paharenko]

Hello.





It is not clear from you message what's the problem. From your

calculations I can see that the length of int field in a flat

file row (BTW please send a piece of your file) is different

in mysqldump programs with different versions? How is the length

of integer fields related to character set? Please provide

more information about the problem and if it is possible send a test

case. 







Vivian Wang <[EMAIL PROTECTED]> wrote:

> [-- text/plain, encoding 7bit, charset: us-ascii, 132 lines --]

> 

> the version is 4.1.12.

> show variables like this,

> 

> | character_set_client| 

> latin1  

> | character_set_connection| 

> latin1  

> | character_set_database  | 

> latin1  

> | character_set_results   | latin1 

> | character_set_server| 

> latin1  

> | character_set_system| 

> utf8

> | character_sets_dir  | 

> /usr/share/mysql/charsets/  

> | collation_connection| 

> latin1_swedish_ci   

> | collation_database  | 

> latin1_swedish_ci   

> | collation_server| latin1_swedish_ci   

> 

> If the table is like test(name char(30), id1 int(4), id2 int(4))

> When I use mysqldump mysql version 3.23.??, l have  the flat file row 

> length is 30+4+4=38.

> When I  use mysqldump mysql verson 4.1.12, I have the flat file row 

> length is 30+11+11=52.

> 

> I tried mysqldump --set-charset=latin2, I still got a row length=52.

> 

> What I should do?

> 

> 

> Gleb Paharenko wrote:

> 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: mysql 4.0 to 4.1 migration and charset problems

[Vivian Wang]

the version is 4.1.12.
show variables like this,

| character_set_client| 
latin1  
| character_set_connection| 
latin1  
| character_set_database  | 
latin1  
| character_set_results   | latin1 
| character_set_server| 
latin1  
| character_set_system| 
utf8
| character_sets_dir  | 
/usr/share/mysql/charsets/  
| collation_connection| 
latin1_swedish_ci   
| collation_database  | 
latin1_swedish_ci   
| collation_server| latin1_swedish_ci   


If the table is like test(name char(30), id1 int(4), id2 int(4))
When I use mysqldump mysql version 3.23.??, l have  the flat file row 
length is 30+4+4=38.
When I  use mysqldump mysql verson 4.1.12, I have the flat file row 
length is 30+11+11=52.


I tried mysqldump --set-charset=latin2, I still got a row length=52.

What I should do?


Gleb Paharenko wrote:


Hello.

I've tested your solution. It doesn't work for users which have SUPER
privilege. This mentioned at:
 http://dev.mysql.com/doc/mysql/en/server-system-variables.html

However, it works with with ordinary users which don't have SUPER
privilege. Here are pieces of my my.cnf (the init_connect is one big string
without line breaks):

[client]

default_character_set=latin1

[mysqld]
default_character_set=latin2
init_connect='SET @lchar = IF(@@session.character_set_client =
_utf8"latin1", @@global.character_set_client,
@@session.character_set_client); set
@@[EMAIL PROTECTED];  set
@@[EMAIL PROTECTED]; set
@@[EMAIL PROTECTED]; '


When root user connects init_connect doesn't execute and we see:
mysql> show variables like '%char%';
+--+---+
| Variable_name| Value   |
+--+---+
| character_set_client | latin1   |
| character_set_connection | latin1   |
| character_set_database   | latin2   |
| character_set_results| latin1   |
| character_set_server | latin2   |
| character_set_system | utf8   |
|


When user without SUPER privilege connects we see:
 | Variable_name| Value   |

+--+---+
| character_set_client | latin2   |
| character_set_connection | latin2   |
| character_set_database   | latin2   |
| character_set_results| latin2   |
| character_set_server | latin2   |
| character_set_system | utf8   |



So it works for me.






 


 http://dev.mysql.com/doc/mysql/en/mysqldump.html
 


Dump & restore was done properly. dump on 4.0, add set names latin2; load i=
nto=20
4.1. The problem is that by default connections from client are as latin1, =
db=20
is latin2 so servers needs to do conversion from latin2->latin1 which can't=
=20
be done and thus I'm getting '?' characters instead of latin2 characters.

The thing I need is how to force default latin2 in all client connections e=
ven=20
if client won't request latin2 by using set names.

Tried doing things like in mysqld.conf:

init-connect =3D SET @lchar =3D IF(@@session.character_set_client =3D _utf8=
"latin1",=20
@@global.character_set_client, @@session.character_set_client); SET=20
character_set_client =3D @lchar; SET character_set_results =3D @lchar; SET=
=20
character_set_connection =3D @lchar;

but that doesn't work unfortunately from init-connect (works from mysql=20
cmdline client) ;-(
=2D-=20
Arkadiusz Mi=B6kiewiczPLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/  http://ftp.pld-linux.org/

   




 

Re: mysql 4.0 to 4.1 migration and charset problems

[Gleb Paharenko]

Hello.





> Any possible problems with this approach?



It is good, if it solved your problems.







>> So it works for me.

> 

> I've ended doing this in a different way. I've created a patch which forces=

> a=20

> file to be read - /etc/mysql/mysql-client.conf (which is the same as .my.cn=

> f)=20

> at mysql_init() time. All clients that use libmysqlclient.so should read it=

> =20

> now.

> 

> http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/mysql-client-config.patch?r=

> ev=3D1.1

> 

> Now I can put defaults in that global config:

> 

> [EMAIL PROTECTED] ~]$ more /etc/mysql/mysql-client.conf

> [client]

> default-character-set=3Dlatin2

> 

> Now all my clients connect with latin2 as default.

> 

> Any possible problems with this approach?

> 

> =2D-=20

> Arkadiusz Mi=B6kiewiczPLD/Linux Team

> http://www.t17.ds.pwr.wroc.pl/~misiek/  http://ftp.pld-linux.org/

> 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: mysql 4.0 to 4.1 migration and charset problems

[Arkadiusz Miskiewicz]

On Monday 11 of July 2005 16:24, Gleb Paharenko wrote:
> Hello.
>
> I've tested your solution. It doesn't work for users which have SUPER
> privilege. This mentioned at:
>   http://dev.mysql.com/doc/mysql/en/server-system-variables.html
>
> However, it works with with ordinary users which don't have SUPER
> privilege. Here are pieces of my my.cnf (the init_connect is one big string
> without line breaks):
>
> [client]
>
> default_character_set=latin1
>
> [mysqld]
> default_character_set=latin2
> init_connect='SET @lchar = IF(@@session.character_set_client =
> _utf8"latin1", @@global.character_set_client,
> @@session.character_set_client); set
> @@[EMAIL PROTECTED];  set
> @@[EMAIL PROTECTED]; set
> @@[EMAIL PROTECTED]; '
[...]
> So it works for me.

I've ended doing this in a different way. I've created a patch which forces a 
file to be read - /etc/mysql/mysql-client.conf (which is the same as .my.cnf) 
at mysql_init() time. All clients that use libmysqlclient.so should read it 
now.

http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/mysql-client-config.patch?rev=1.1

Now I can put defaults in that global config:

[EMAIL PROTECTED] ~]$ more /etc/mysql/mysql-client.conf
[client]
default-character-set=latin2

Now all my clients connect with latin2 as default.

Any possible problems with this approach?

-- 
Arkadiusz MiśkiewiczPLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/  http://ftp.pld-linux.org/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: mysql 4.0 to 4.1 migration and charset problems

[Gleb Paharenko]

Hello.



I've tested your solution. It doesn't work for users which have SUPER

privilege. This mentioned at:

  http://dev.mysql.com/doc/mysql/en/server-system-variables.html



However, it works with with ordinary users which don't have SUPER

privilege. Here are pieces of my my.cnf (the init_connect is one big string

without line breaks):



[client]



default_character_set=latin1



[mysqld]

default_character_set=latin2

init_connect='SET @lchar = IF(@@session.character_set_client =

_utf8"latin1", @@global.character_set_client,

@@session.character_set_client); set

@@[EMAIL PROTECTED];  set

@@[EMAIL PROTECTED]; set

@@[EMAIL PROTECTED]; '





When root user connects init_connect doesn't execute and we see:

 mysql> show variables like '%char%';

 
+--+---+

 | Variable_name| Value   |

 
+--+---+

 | character_set_client | latin1   |

 | character_set_connection | latin1   |

 | character_set_database   | latin2   |

 | character_set_results| latin1   |

 | character_set_server | latin2   |

 | character_set_system | utf8   |

 |





When user without SUPER privilege connects we see:

  | Variable_name| Value   |


+--+---+

| character_set_client | latin2   |

| character_set_connection | latin2   |

| character_set_database   | latin2   |

| character_set_results| latin2   |

| character_set_server | latin2   |

| character_set_system | utf8   |







So it works for me.













>>   http://dev.mysql.com/doc/mysql/en/mysqldump.html

> Dump & restore was done properly. dump on 4.0, add set names latin2; load i=

> nto=20

> 4.1. The problem is that by default connections from client are as latin1, =

> db=20

> is latin2 so servers needs to do conversion from latin2->latin1 which can't=

> =20

> be done and thus I'm getting '?' characters instead of latin2 characters.

> 

> The thing I need is how to force default latin2 in all client connections e=

> ven=20

> if client won't request latin2 by using set names.

> 

> Tried doing things like in mysqld.conf:

> 

> init-connect =3D SET @lchar =3D IF(@@session.character_set_client =3D _utf8=

> "latin1",=20

> @@global.character_set_client, @@session.character_set_client); SET=20

> character_set_client =3D @lchar; SET character_set_results =3D @lchar; SET=

> =20

> character_set_connection =3D @lchar;

> 

> but that doesn't work unfortunately from init-connect (works from mysql=20

> cmdline client) ;-(

> =2D-=20

> Arkadiusz Mi=B6kiewiczPLD/Linux Team

> http://www.t17.ds.pwr.wroc.pl/~misiek/  http://ftp.pld-linux.org/

> 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: mysql 4.0 to 4.1 migration and charset problems

[Arkadiusz Miskiewicz]

On Thursday 07 of July 2005 00:16, Gleb Paharenko wrote:
> Hello.
>
>
> For a pity, I could give explanations only for your query about
> selecting @@global.xxx variables. I think server returns correct
> results, because you're selecting global variables, while
> character_set_client, character_set_connection, character_set_results
> are session  variables. And with SET NAMES you're setting
> @@character_xxx variables which are synonym for @@session.character_xxx.
I see.

> In what way have you done your upgrade? If you haven't used mysqldump
> you could get some problems. Make the dump, and restore it setting
> the correct connection variables for mysql program. Be aware of that
> mysqldump could put SET NAMES at the beginning of the dump file. Use
> set-names=latin2 for it. See:
>   http://dev.mysql.com/doc/mysql/en/mysqldump.html
Dump & restore was done properly. dump on 4.0, add set names latin2; load into 
4.1. The problem is that by default connections from client are as latin1, db 
is latin2 so servers needs to do conversion from latin2->latin1 which can't 
be done and thus I'm getting '?' characters instead of latin2 characters.

The thing I need is how to force default latin2 in all client connections even 
if client won't request latin2 by using set names.

Tried doing things like in mysqld.conf:

init-connect = SET @lchar = IF(@@session.character_set_client = _utf8"latin1", 
@@global.character_set_client, @@session.character_set_client); SET 
character_set_client = @lchar; SET character_set_results = @lchar; SET 
character_set_connection = @lchar;

but that doesn't work unfortunately from init-connect (works from mysql 
cmdline client) ;-(
-- 
Arkadiusz MiśkiewiczPLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/  http://ftp.pld-linux.org/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: mysql 4.0 to 4.1 migration and charset problems

[Gleb Paharenko]

Hello.





For a pity, I could give explanations only for your query about

selecting @@global.xxx variables. I think server returns correct

results, because you're selecting global variables, while 

character_set_client, character_set_connection, character_set_results

are session  variables. And with SET NAMES you're setting

@@character_xxx variables which are synonym for @@session.character_xxx.

In what way have you done your upgrade? If you haven't used mysqldump

you could get some problems. Make the dump, and restore it setting

the correct connection variables for mysql program. Be aware of that

mysqldump could put SET NAMES at the beginning of the dump file. Use

set-names=latin2 for it. See:

  http://dev.mysql.com/doc/mysql/en/mysqldump.html









Arkadiusz Miskiewicz <[EMAIL PROTECTED]> wrote:

> Hi,

> 

> I have mysql 4.0  db with configuration:

> set-variable =3D default-character-set=3Dlatin2

> set-variable =3D character-set=3Dlatin2

> 

> now I'm trying to migrate to mysql 4.1.12 My current config is:

> character-set-server=3Dlatin2

> collation-server=3Dlatin2_general_ci

> 

> The problem is connection/reply/client-character set. mysql 4.1 by default=

> =20

> uses 'latin1' so in all queries (from previously latin2 mysql 4.0 database)=

> I=20

> don't have latin2 characters just '?' chars. That's obvious because due to=

> =20

> default latin1 in 4.1.

> 

> SET NAMES 'latin2' from client side of coruse cures whole problem but... I=

> =20

> can't fix every possible application that my users have installed (and if=20

> there are thousands of users this is simply impossible).

> 

> What's the proper way of dealing with this problem? I've tried to use some=

> =20

> nasty hacks like init-connect=3D"SET NAMES latin2" and this half-works - I =

> see=20

> latin2 characters in server responses... but it breaks for example phpmyadm=

> in=20

> (characters are broken in results; when I drop init-connect hack phpmyadmin=

> =20

> works nicely). So init-connect isn't usable.

> 

> Now when connecting with mysql command line client then I by default get=20

> latin1 but can change easily to latin2 using=20

> [mysql]

> default-character-set=3Dlatin2

> in .my.cnf file. That's great but this works only for mysql cmd line client=

> =20

> _only_ while my primary concern is php.

> 

> Now is the funny part, there is no .my.cnf file, I connect with mysql cmdli=

> ne.

> mysql> \s

> =2D-

> mysql  Ver 14.7 Distrib 4.1.12, for pld-linux-gnu (powerpc) using readline =

> 4.3

> 

> Connection id:  2

> Current database:

> Current user:   [EMAIL PROTECTED]

> SSL:Not in use

> Current pager:  stdout

> Using outfile:  ''

> Using delimiter:;

> Server version: 4.1.12-log

> Protocol version:   10

> Connection: Localhost via UNIX socket

> Server characterset:latin2

> Db characterset:latin2

> Client characterset:latin1

> Conn.  characterset:latin1

> UNIX socket:/var/lib/mysql/mysql.sock

> Uptime: 34 min 35 sec

> 

> Threads: 1  Questions: 12  Slow queries: 0  Opens: 11  Flush tables: 1  Ope=

> n=20

> tables: 0  Queries per second avg: 0.006

> =2D-

> 

> mysql> show variables like '%char%';

> +--++

> | Variable_name| Value  |

> +--++

> | character_set_client | latin1 |

> | character_set_connection | latin1 |

> | character_set_database   | latin2 |

> | character_set_results| latin1 |

> | character_set_server | latin2 |

> | character_set_system | utf8   |

> | character_sets_dir   | /usr/share/mysql/charsets/ |

> +--++

> 7 rows in set (0.00 sec)

> 

> As you can see client/connection/results are latin1 BUT:

> 

> mysql> select @@global.character_set_client,=20

> @@global.character_set_connection, @@global.character_set_database,=20

> @@global.character_set_results, @@global.character_set_results,=20

> @@global.character_set_server;

> +---+---+--=

> =2D--++=

> =2D---+---+

> | @@global.character_set_client | @@global.character_set_connection |=20

> @@global.character_set_database | @@global.character_set_results |=20

> @@global.character_set_results | @@global.character_set_server |

> +---+---+--=

> =2D--++=

> =2D---+---+

> | 

Re: MySQL 4.0 and concat

[William R. Mussatto]

A bit of a warning, if the fields are DATETIME rather than DATE, add the
appropriate hours:minutes:seconds to the test
WHERE datetimefield >'1999-02-01 23:59:59'. When comparing DATETIME fields
with date strings '00:00:00' is assumed and that can cause problems if one
forgets that.
> Have you considered NOT comparing dates as strings but rather as date
> values?  That will avoid the use of CONCAT() completely.
>
>
> SELECT *
> FROM sampletable
> WHERE datefield >= '1999-01-12' and datefield <'1999-02-01'
>
> This example query will get all of the records from sampletable that
> were  entered after January 11th and before February 1st. It will also
> be  **very** fast if the column "datefield" is indexed.
>
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>
> Alfredo Cole <[EMAIL PROTECTED]> wrote on 10/11/2004 09:43:14 AM:
>
>> Hi:
>>
>> I have a problem in that all statements that include concat execute
>> very
>
>> slowly. For instance, if I have three fields in string format  that
> represent
>> a year, month and day, and want to issue a select like:
>>
>> select * from cxcmanpag where contact
>> (year,month,day)<=stringYear+stringMonth+stringDay (simplified), then
>> it
> will
>> take a long time, againts a table with only around 100,00 records. If
>> I  rewrite the statement to read:
>>
>> select * from cxcmanpag where year<=stringYear and month<=stringMonth
> and
>> day<=stringDay, it will execute considerable faster, but will not
> produce the
>> same results.
>>
>> I have looked in the manual, and also read High Performance MySQL
>> from Zawodny
>> and Balling, and MySQL from Paul Dubois, but none of them seem to
> address
>> this issue.
>>
>> Can somebody point me to a URL or book that I should be reading to
> improve,
>> this, or how to avoid using concat altogether?
>>
>> Thank you.
>>
>> --
>> Alfredo J. Cole
>> Grupo ACyC
>> www.acyc.com - www.clshonduras.com - SolCom


-- 
William R. Mussatto, Senior Systems Engineer
Ph. 909-920-9154 ext. 27
FAX. 909-608-7061



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Fwd: Re: MySQL 4.0 and concat

[Alfredo Cole]

Sorry. This should have gone back to the list.

--  Mensaje reenviado  --

Subject: Re: MySQL 4.0 and concat
Date: Lun 11 Oct 2004 11:37
From: Alfredo Cole <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]

El Lun 11 Oct 2004 08:35, escribió:
> Have you considered NOT comparing dates as strings but rather as date
> values?  That will avoid the use of CONCAT() completely.

I will try this. But there will always be times when using concat might be
required. It would be nice to know if there is a solution to the concat
problem.

Thank you, and regards.

--
Alfredo J. Cole
Grupo ACyC
www.acyc.com - www.clshonduras.com - SolCom

---

-- 
Alfredo J. Cole
Grupo ACyC
www.acyc.com - www.clshonduras.com - SolCom

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 and concat

[SGreen]

Have you considered NOT comparing dates as strings but rather as date 
values?  That will avoid the use of CONCAT() completely.


SELECT * 
FROM sampletable
WHERE datefield >= '1999-01-12' and datefield <'1999-02-01'

This example query will get all of the records from sampletable that were 
entered after January 11th and before February 1st. It will also be 
**very** fast if the column "datefield" is indexed.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine

Alfredo Cole <[EMAIL PROTECTED]> wrote on 10/11/2004 09:43:14 AM:

> Hi:
> 
> I have a problem in that all statements that include concat execute very 

> slowly. For instance, if I have three fields in string format  that 
represent 
> a year, month and day, and want to issue a select like:
> 
> select * from cxcmanpag where contact 
> (year,month,day)<=stringYear+stringMonth+stringDay (simplified), then it 
will 
> take a long time, againts a table with only around 100,00 records. If I 
> rewrite the statement to read:
> 
> select * from cxcmanpag where year<=stringYear and month<=stringMonth 
and 
> day<=stringDay, it will execute considerable faster, but will not 
produce the 
> same results.
> 
> I have looked in the manual, and also read High Performance MySQL 
> from Zawodny 
> and Balling, and MySQL from Paul Dubois, but none of them seem to 
address 
> this issue.
> 
> Can somebody point me to a URL or book that I should be reading to 
improve, 
> this, or how to avoid using concat altogether?
> 
> Thank you.
> 
> -- 
> Alfredo J. Cole
> Grupo ACyC
> www.acyc.com - www.clshonduras.com - SolCom
> 
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
> 

Re: Mysql 4.0 windows XP Downloads

[Julian]

Francois,
You didn't reply to the list, just to me. If you reply to the list, more 
people will be able to help you. I'm quite new myself.

You need to set up user accounts. Download an admin program such as 
MySQL Control Center. Maybe there are better ones, but that's what I 
use. You can do a lot of stuff with this and save your self from having 
to type at the command line.

MySql Control Center
http://dev.mysql.com/downloads/other/mysqlcc.html
Julian
Francois A. Atallah wrote:
Y I'm getting this error every time I want to access the mysql database
ERROR 1044: Access denied for user: '@localhost' to database 'mysql'
I can only bypass this error if I use -u root ? 

Thanks,
Francois A
-Original Message-
From: Julian [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 20, 2004 12:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Mysql 4.0 windows XP Downloads

That's it. You had it. x86 refers to the Intel chip family not the operating
system. I'm using that quite happily on XP.
Julian
Francois A. Atallah wrote:
May someone please send me the link to download mysql Binary 
distribution for the first time on windows XP, I have looked into 
mysql/downloads and they only have X86.

Thanks,
Francois A


.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Mysql 4.0 windows XP Downloads

[jeffrey_n_Dyke]

> May someone please send me the link to download mysql Binary distribution
> for the first time on windows XP, I have looked into mysql/downloads and
> they only have X86.

Windows XP, and every other windows platform, runs on X86 architecture.
That is the download you want.

Jeff








-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0.x charset

[Jean-Marc PULVAR]

It's possibly due to your ssh connection but I couldn't answer you about 
this because I only use mysql with phpmyadmin.

Regards
Yves wrote:
Thanks,
As it turns out, I was trying show variables like --
And had a syntax mistake
Does SHOW VARIABLES only show a certain number of
lines? When I ran this command, character_set was not
listed... the list seemed cut off just before it.
Unless it is an issue with SSH only showing x amount
of lines..
thanks,
Yves A
 --- Jean-Marc PULVAR <[EMAIL PROTECTED]> wrote: 

You can see it by executing the "SHOW VARIABLES"
query on your server. 
You will find the used charset in the
'character_set' variable.

You can also use the query "SHOW VARIABLES LIKE
'character_set'" which 
will directly match what you want.

Yves wrote:

Hello,
How can I see what char set is being used as the
default char set on the server or database?
Also, is there a way to change the default
setting?
Thanks,
Yves


__
Post your free ad now! http://personals.yahoo.ca
--
---
 ___   _
 __ / __\ ___   ___  _ __ | |_ _   _
(__)   /__\/// _ \ / _ \| '_ \| __| | | |
 ||   / \/  \ (_) | (_) | | | | |_| |_| |
 ||   \_/\___/ \___/|_| |_|\__|\__, |
 ___|""|__.._  |___/
/\
\/~~~ Jean-Marc PULVAR (Web
Programmer)
  Boonty SA
  4 bis villa du mont tonnerre
  75015 PARIS
---


__ 
Post your free ad now! http://personals.yahoo.ca

--
---
 ___   _
 __ / __\ ___   ___  _ __ | |_ _   _
(__)   /__\/// _ \ / _ \| '_ \| __| | | |
 ||   / \/  \ (_) | (_) | | | | |_| |_| |
 ||   \_/\___/ \___/|_| |_|\__|\__, |
 ___|""|__.._  |___/
/\
\/~~~ Jean-Marc PULVAR (Web Programmer)
  Boonty SA
  4 bis villa du mont tonnerre
  75015 PARIS
---
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0.x charset

[Yves]

Thanks,

As it turns out, I was trying show variables like --

And had a syntax mistake

Does SHOW VARIABLES only show a certain number of
lines? When I ran this command, character_set was not
listed... the list seemed cut off just before it.

Unless it is an issue with SSH only showing x amount
of lines..

thanks,

Yves A

 --- Jean-Marc PULVAR <[EMAIL PROTECTED]> wrote: 
> You can see it by executing the "SHOW VARIABLES"
> query on your server. 
> You will find the used charset in the
> 'character_set' variable.
> 
> You can also use the query "SHOW VARIABLES LIKE
> 'character_set'" which 
> will directly match what you want.
> 
> Yves wrote:
> 
> > Hello,
> > 
> > How can I see what char set is being used as the
> > default char set on the server or database?
> > 
> > Also, is there a way to change the default
> setting?
> > 
> > Thanks,
> > 
> > Yves
> > 
> >
>
__
> 
> > Post your free ad now! http://personals.yahoo.ca
> > 
> 
> -- 
>
---
>   ___   _
>   __ / __\ ___   ___  _ __ | |_ _   _
>  (__)   /__\/// _ \ / _ \| '_ \| __| | | |
>   ||   / \/  \ (_) | (_) | | | | |_| |_| |
>   ||   \_/\___/ \___/|_| |_|\__|\__, |
>   ___|""|__.._  |___/
> /\
> \/~~~ Jean-Marc PULVAR (Web
> Programmer)
>Boonty SA
>4 bis villa du mont tonnerre
>75015 PARIS
>
---
>  

__ 
Post your free ad now! http://personals.yahoo.ca

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0.x charset

[Jean-Marc PULVAR]

You can see it by executing the "SHOW VARIABLES" query on your server. 
You will find the used charset in the 'character_set' variable.

You can also use the query "SHOW VARIABLES LIKE 'character_set'" which 
will directly match what you want.

Yves wrote:
Hello,
How can I see what char set is being used as the
default char set on the server or database?
Also, is there a way to change the default setting?
Thanks,
Yves
__ 
Post your free ad now! http://personals.yahoo.ca

--
---
 ___   _
 __ / __\ ___   ___  _ __ | |_ _   _
(__)   /__\/// _ \ / _ \| '_ \| __| | | |
 ||   / \/  \ (_) | (_) | | | | |_| |_| |
 ||   \_/\___/ \___/|_| |_|\__|\__, |
 ___|""|__.._  |___/
/\
\/~~~ Jean-Marc PULVAR (Web Programmer)
  Boonty SA
  4 bis villa du mont tonnerre
  75015 PARIS
---
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Mysql 4.0 -Oracle Stored Procedure Trigger Conversion

[Daniel Kasak]

Garg, Piyush (EM, GECIS) wrote:

  Hi Everybody,

Is there any way we can tranform the Stores procedure and Triggers present under Oracle Custom Application to mysql.
Please tell ways or any tools which can help us rewrite the logic in Mysql.

Thanks and regards,
Piyush
  

Stored Procedures are only supported in version 5.0.x and above ( which
is currnetly a development release ).
Triggers will be longer still.
You can get trigger-like functionality by creating functions in your
application to manage the updating of your DB, and always using those
functions instead of talking directly to the DB server. This is more
flexible, but slower. Anyway, it's the only option currently.

Dan

-- 

signature
Daniel Kasak

IT Developer

NUS Consulting Group

Level 5, 77 Pacific Highway

North Sydney, NSW, Australia 2060

T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989

email: [EMAIL PROTECTED]

website: http://www.nusconsulting.com.au



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 - Download - Viruses ?

[Paul DuBois]

At 17:25 -0700 3/16/04, Sasha Pachev wrote:
Kevin Carpenter wrote:
While downloading this a I got a number of virus warnings from 
McAfee.  I aborted the download.

Anyone else experienced this?

I emailed MySQL but didn't hear back.
Kevin:

Were you downloading a Windows or some other binary? If it was 
Windows, I would be concerned - the build machine could have gotten 
infected. The unfortunate thing is that MySQL build team could very 
easily miss it because so many Windows machines out there are 
already infected anyway that spreading a virus through the Windows 
binary would probably not make things that much worse.
I hope everyone recognizes that this is speculation.


If it was some other binary, this is fairly common - by an odd 
coincidence tar.gz of MySQL binary contains byte strings similar to 
some viruses known to McAfee. There is no reasonable way a 
non-Windows tar.gz could infect a Windows machine. A theoretical 
possibility, of course, exists, but the Earth being hit by a large 
asteroid by tonight is more likely.

--
Sasha Pachev
Create online surveys at http://www.surveyz.com/


--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
MySQL Users Conference: April 14-16, 2004
http://www.mysql.com/uc2004/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 - Download - Viruses ?

[Sasha Pachev]

Kevin Carpenter wrote:
While downloading this a I got a number of virus warnings from McAfee.  I aborted the download.

Anyone else experienced this?

I emailed MySQL but didn't hear back.
Kevin:

Were you downloading a Windows or some other binary? If it was Windows, I would 
be concerned - the build machine could have gotten infected. The unfortunate 
thing is that MySQL build team could very easily miss it because so many Windows 
machines out there are already infected anyway that spreading a virus through 
the Windows binary would probably not make things that much worse.

If it was some other binary, this is fairly common - by an odd coincidence 
tar.gz of MySQL binary contains byte strings similar to some viruses known to 
McAfee. There is no reasonable way a non-Windows tar.gz could infect a Windows 
machine. A theoretical possibility, of course, exists, but the Earth being hit 
by a large asteroid by tonight is more likely.

--
Sasha Pachev
Create online surveys at http://www.surveyz.com/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 crashed; Please help

[vpendleton]

Here are the instructions for doing a stack trace.

http://www.mysql.com/doc/en/Using_stack_trace.html

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 2/13/04, 2:24:30 PM, Jacob Friis Larsen "(Eksperten" "admin)" 
<[EMAIL PROTECTED]> wrote regarding Re: MySQL 4.0 crashed; Please help:


> [EMAIL PROTECTED] wrote:
> > Did you perform a stack trace?

> No, how do I do that?

> /Jacob

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 crashed; Please help

[Jacob Friis Larsen (Eksperten admin)]

[EMAIL PROTECTED] wrote:
Did you perform a stack trace?
No, how do I do that?

/Jacob

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 crashed; Please help

[vpendleton]

Did you perform a stack trace?

>> Original Message <<

On 2/13/04, 2:36:42 AM, Jacob Friis Larsen "[Eksperten" "admin]" 
<[EMAIL PROTECTED]> wrote regarding MySQL 4.0 crashed; Please help:


> Can someone help me find out what caused this crash?
> My system is a Red Hat 7.3 on a HP Netserver LC2000, dual PIII 800mhz
> with 2.5G ram. 3 disks in raid 5.

> The MySQL database is 4.0.17

> 040212 19:27:36  read_const: Got error 126 when reading table
> ./exp4/sql_cache

> Number of processes running now: 0
> 040212 19:28:04  mysqld restarted
> InnoDB: Fatal error: cannot allocate 1073758208 bytes of
> InnoDB: memory with malloc! Total allocated memory
> InnoDB: by InnoDB 24482732 bytes. Operating system errno: 12
> InnoDB: Cannot continue operation!
> InnoDB: Check if you should increase the swap file or
> InnoDB: ulimits of your operating system.
> InnoDB: On FreeBSD check you have compiled the OS with
> InnoDB: a big enough maximum process size.
> InnoDB: We now intentionally generate a seg fault so that
> InnoDB: on Linux we get a stack trace.
> mysqld got signal 11;
> This could be because you hit a bug. It is also possible that this binary
> or one of the libraries it was linked against is corrupt, improperly 
built,
> or misconfigured. This error can also be caused by malfunctioning 
hardware.
> We will try our best to scrape up some info that will hopefully help
> diagnose
> the problem, but since we have already crashed, something is definitely
> wrong
> and this may fail.

> key_buffer_size=402653184
> read_buffer_size=1044480
> max_used_connections=0
> max_connections=800
> threads_connected=0
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
> = 291705 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.

> thd=0x8450b80
> Attempting backtrace. You can use the following information to find out
> where mysqld died. If you see no messages after this, something went
> terribly wrong...
> Bogus stack limit or frame pointer, fp=0xbfffe718,
> stack_bottom=0x58575655, thread_stack=126976, aborting backtrace.
> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort...
> thd->query at 0x54535251  is invalid pointer
> thd->thread_id=1601790316
> The manual page at http://www.mysql.com/doc/en/Crashing.html contains
> information that should help you find out what is causing the crash.
> 040212 19:28:06  mysqld ended

> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 Installation Problem -- trying again

[Michael Stassen]

In one message you say you've run mysql_install_db, in another you say 
you're logged in as root.  In your second message, you say you got the error

  Fatal error: Can't open privilege tables: Can't find file:
  './mysql/host.frm' (errno 13) ...
You can use perror to translate the error number (13) to text.

  # perror 13
  Error code  13:  Permission denied
I expect you ran mysql_install_db as root, so root owns the data 
directory and files.  Hence, the mysql user cannot read them.   I know 
you say that you've used chown to reset the ownership, but I think the 
most likely explanation is that you've missed something.  As root, cd to 
the mysql data directory and run

  chown -R mysql:mysql .

Then try mysqld_safe again.

Michael

Zhao, Charles wrote:

Thanks ... but yeas, I have done both and still got that ... that's why
I was asking the questions.
 
I have 3.23 that came with my Linux distribution and it's not
uninstalled -- but I don't think that should be the cause, though.

	-Original Message-
	From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
	Sent: Thursday, January 08, 2004 10:36 AM
	To: [EMAIL PROTECTED]
	Subject: RE: MySQL 4.0 Installation Problem -- trying again
	
	

	Charles, 

	First, you need to run the mysql_install_db script.  That will
create the initial mysql database tables which is where security is
tracked.  Next, you will need to use the chown command to change the
ownership of your mysql data directory (and I would include the logging
directory, too) to be owned by mysql both as user and group. 

	Once these two steps are finished, it should run for you. 

	Dave 

	David Christensen 
	Brokers International, Ltd. 
	1200 E Main St 
	PO Box 160 
	Panora, IA  50216 
	(800) 362-1097 or (641) 755-2775 
	[EMAIL PROTECTED] 
	  

	-Original Message- 
	From: Zhao, Charles [mailto:[EMAIL PROTECTED] 
	Sent: Thursday, January 08, 2004 12:22 PM 
	To: [EMAIL PROTECTED] 
	Subject: MySQL 4.0 Installation Problem -- trying again 

	OK I was wrong: those files are mentioned in the doc, but I
strictly followed the manual and I still got those errors. 
	  
	The first problem is host.frm cannot be found while starting
mysqld (when starting InnoDB) (in the mysqld.log file), and the server
start aborted.  The manual says script/mysql_install_db will set the
initial grant tables for me and I don't need to worrry about that before
the server starts.  But I still get that error.  I am logged in as
"root".

	
	I installed Mysql on NT a long time ago and that was easy. 
	  
	Any help? 
	  
	Thanks. 

	-Original Message- 
	From: Zhao, Charles 
	Sent: Wednesday, January 07, 2004 5:14 PM 
	To: '[EMAIL PROTECTED]' 
	Subject: RE: MySQL 4.0 Installation Problem 
	
	
	Fatal error: Can't open privilege tables: Can't find
file: './mysql/host.frm' (errno 13) ... 
	 
	Well, since I failed to use RPM to install MySQL 4.0
over 3.23 
	-- I am not sure if I have to unstall the latter before I
install the former, the manual does not mention that, I went ahead to do
a fresh binary installation of it on my Linux 7, under usr/local/
directory. Followed the manual step by step until I started the server:

	/bin/mysqld_safe & (also tried it with parameter
user=mysql), 
	but I got "mysql ended ... [1]+ Done
./bin/mysqld_safe" msg, 
	 
	and I could not run any further commands, failing with
msgs like "Can't connect to local MySQL server though socket
'/tmp/mysql.sock', Check that mysqld is running and that the socket:
'/tmp/mysql.sock' exists!"

	 
	then I found in the sql log file: "Fatal error: Can't
open privilege tables: Can't find file: './mysql/host.frm' (errno 13)
..." when starting the InnoDB tables.

	 
	Both files mysql.sock and host.frm are not mentioned in
the manual, and not found in my file system. 
	 
	Any one can point out the problem? 
	 
	Thanks. 

	-Original Message- 
	From: Zhao, Charles 
	Sent: Tuesday, January 06, 2004 4:53 PM 
	To: '[EMAIL PROTECTED]' 
	Subject: MySQL 4.0 Installation Problem 
	
	
	I have 3.23 that comes with my Linux
distribution, now 
	when I tried to do a rpm installation of 4.0, I got messages
like: 
	"warning: MySQL-server-4.0.17 ... .rpm: V3 DSA 
	signature: NOKEY, key ID ..., 
	file /usr/bin/mysql from install of 
	MySQL-client-4.0.17.0 conflicts with file from package
mysql-3.23.52-3 
	... 
	file /usr/shar/man/man1/ ... from install of ...

	conflicts with file from package mysql-3.23... 
	  

RE: MySQL 4.0 Installation Problem -- trying again

[DChristensen]

What does the .err file tell you?  

-Original Message-
From: Zhao, Charles [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 08, 2004 12:39 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: MySQL 4.0 Installation Problem -- trying again


Thanks ... but yeas, I have done both and still got that ... that's why I
was asking the questions.
 
I have 3.23 that came with my Linux distribution and it's not uninstalled --
but I don't think that should be the cause, though.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 08, 2004 10:36 AM
To: [EMAIL PROTECTED]
Subject: RE: MySQL 4.0 Installation Problem -- trying again



Charles, 

First, you need to run the mysql_install_db script.  That will create the
initial mysql database tables which is where security is tracked.  Next, you
will need to use the chown command to change the ownership of your mysql
data directory (and I would include the logging directory, too) to be owned
by mysql both as user and group. 

Once these two steps are finished, it should run for you. 

Dave 

David Christensen 
Brokers International, Ltd. 
1200 E Main St 
PO Box 160 
Panora, IA  50216 
(800) 362-1097 or (641) 755-2775 
[EMAIL PROTECTED] 
  


-Original Message- 
From: Zhao, Charles [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ] 
Sent: Thursday, January 08, 2004 12:22 PM 
To: [EMAIL PROTECTED] 
Subject: MySQL 4.0 Installation Problem -- trying again 


OK I was wrong: those files are mentioned in the doc, but I strictly
followed the manual and I still got those errors. 
  
The first problem is host.frm cannot be found while starting mysqld (when
starting InnoDB) (in the mysqld.log file), and the server start aborted.
The manual says script/mysql_install_db will set the initial grant tables
for me and I don't need to worrry about that before the server starts.  But
I still get that error.  I am logged in as "root".


I installed Mysql on NT a long time ago and that was easy. 
  
Any help? 
  
Thanks. 

-Original Message- 
From: Zhao, Charles 
Sent: Wednesday, January 07, 2004 5:14 PM 
To: '[EMAIL PROTECTED]' 
Subject: RE: MySQL 4.0 Installation Problem 


Fatal error: Can't open privilege tables: Can't find file:
'./mysql/host.frm' (errno 13) ... 
 
Well, since I failed to use RPM to install MySQL 4.0 over 3.23 
-- I am not sure if I have to unstall the latter before I install the
former, the manual does not mention that, I went ahead to do a fresh binary
installation of it on my Linux 7, under usr/local/ directory. Followed the
manual step by step until I started the server:

/bin/mysqld_safe & (also tried it with parameter user=mysql), 
but I got "mysql ended ... [1]+ Done./bin/mysqld_safe" msg, 
 
and I could not run any further commands, failing with msgs like
"Can't connect to local MySQL server though socket '/tmp/mysql.sock', Check
that mysqld is running and that the socket: '/tmp/mysql.sock' exists!"

 
then I found in the sql log file: "Fatal error: Can't open privilege
tables: Can't find file: './mysql/host.frm' (errno 13) ..." when starting
the InnoDB tables.

 
Both files mysql.sock and host.frm are not mentioned in the manual,
and not found in my file system. 
 
Any one can point out the problem? 
 
Thanks. 

-Original Message- 
From: Zhao, Charles 
Sent: Tuesday, January 06, 2004 4:53 PM 
To: '[EMAIL PROTECTED]' 
Subject: MySQL 4.0 Installation Problem 


I have 3.23 that comes with my Linux distribution, now 
when I tried to do a rpm installation of 4.0, I got messages like: 
"warning: MySQL-server-4.0.17 ... .rpm: V3 DSA 
signature: NOKEY, key ID ..., 
file /usr/bin/mysql from install of 
MySQL-client-4.0.17.0 conflicts with file from package mysql-3.23.52-3 
... 
file /usr/shar/man/man1/ ... from install of ... 
conflicts with file from package mysql-3.23... 
..." 
and the conflict list goes on. 
 
The installation manual does not seem to discuss about 
such issues.  Do I need to remove my 3.23 before I run the installation? 
-- but that's not what the manual says, though.  The first warning msg, is
that a problem, too? 
 
Thanks. 

RE: MySQL 4.0 Installation Problem -- trying again

[Zhao, Charles]

Thanks ... but yeas, I have done both and still got that ... that's why
I was asking the questions.
 
I have 3.23 that came with my Linux distribution and it's not
uninstalled -- but I don't think that should be the cause, though.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 08, 2004 10:36 AM
To: [EMAIL PROTECTED]
        Subject: RE: MySQL 4.0 Installation Problem -- trying again



Charles, 

First, you need to run the mysql_install_db script.  That will
create the initial mysql database tables which is where security is
tracked.  Next, you will need to use the chown command to change the
ownership of your mysql data directory (and I would include the logging
directory, too) to be owned by mysql both as user and group. 

Once these two steps are finished, it should run for you. 

Dave 

David Christensen 
Brokers International, Ltd. 
1200 E Main St 
PO Box 160 
Panora, IA  50216 
(800) 362-1097 or (641) 755-2775 
[EMAIL PROTECTED] 
  


-Original Message- 
From: Zhao, Charles [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 08, 2004 12:22 PM 
To: [EMAIL PROTECTED] 
Subject: MySQL 4.0 Installation Problem -- trying again 


OK I was wrong: those files are mentioned in the doc, but I
strictly followed the manual and I still got those errors. 
  
The first problem is host.frm cannot be found while starting
mysqld (when starting InnoDB) (in the mysqld.log file), and the server
start aborted.  The manual says script/mysql_install_db will set the
initial grant tables for me and I don't need to worrry about that before
the server starts.  But I still get that error.  I am logged in as
"root".


I installed Mysql on NT a long time ago and that was easy. 
  
Any help? 
  
Thanks. 

-Original Message- 
From: Zhao, Charles 
Sent: Wednesday, January 07, 2004 5:14 PM 
To: '[EMAIL PROTECTED]' 
Subject: RE: MySQL 4.0 Installation Problem 


Fatal error: Can't open privilege tables: Can't find
file: './mysql/host.frm' (errno 13) ... 
 
Well, since I failed to use RPM to install MySQL 4.0
over 3.23 
-- I am not sure if I have to unstall the latter before I
install the former, the manual does not mention that, I went ahead to do
a fresh binary installation of it on my Linux 7, under usr/local/
directory. Followed the manual step by step until I started the server:

/bin/mysqld_safe & (also tried it with parameter
user=mysql), 
but I got "mysql ended ... [1]+ Done
./bin/mysqld_safe" msg, 
 
and I could not run any further commands, failing with
msgs like "Can't connect to local MySQL server though socket
'/tmp/mysql.sock', Check that mysqld is running and that the socket:
'/tmp/mysql.sock' exists!"

 
then I found in the sql log file: "Fatal error: Can't
open privilege tables: Can't find file: './mysql/host.frm' (errno 13)
..." when starting the InnoDB tables.

 
Both files mysql.sock and host.frm are not mentioned in
the manual, and not found in my file system. 
 
Any one can point out the problem? 
 
Thanks. 

-Original Message- 
From: Zhao, Charles 
Sent: Tuesday, January 06, 2004 4:53 PM 
To: '[EMAIL PROTECTED]' 
Subject: MySQL 4.0 Installation Problem 


I have 3.23 that comes with my Linux
distribution, now 
when I tried to do a rpm installation of 4.0, I got messages
like: 
"warning: MySQL-server-4.0.17 ... .rpm: V3 DSA 
signature: NOKEY, key ID ..., 
file /usr/bin/mysql from install of 
MySQL-client-4.0.17.0 conflicts with file from package
mysql-3.23.52-3 
... 
file /usr/shar/man/man1/ ... from install of ...

conflicts with file from package mysql-3.23... 
..." 
and the conflict list goes on. 
 
The installation manual does not seem to discuss
about 
such issues.  Do I need to remove my 3.23 before I run the
installation? 
-- but that's not what the manual says, though.  The first
warning msg, is that a problem, too? 
 
Thanks. 

RE: MySQL 4.0 Installation Problem

[Zhao, Charles]

Fatal error: Can't open privilege tables: Can't find file:
'./mysql/host.frm' (errno 13) ...
 
Well, since I failed to use RPM to install MySQL 4.0 over 3.23 -- I am
not sure if I have to unstall the latter before I install the former,
the manual does not mention that, I went ahead to do a fresh binary
installation of it on my Linux 7, under usr/local/ directory.  Followed
the manual step by step until I started the server:
/bin/mysqld_safe & (also tried it with parameter user=mysql),
but I got "mysql ended ... [1]+ Done./bin/mysqld_safe" msg,
 
and I could not run any further commands, failing with msgs like "Can't
connect to local MySQL server though socket '/tmp/mysql.sock', Check
that mysqld is running and that the socket: '/tmp/mysql.sock' exists!"
 
then I found in the sql log file: "Fatal error: Can't open privilege
tables: Can't find file: './mysql/host.frm' (errno 13) ..." when
starting the InnoDB tables.
 
Both files mysql.sock and host.frm are not mentioned in the manual, and
not found in my file system.
 
Any one can point out the problem?
 
Thanks.

-Original Message-
From: Zhao, Charles 
Sent: Tuesday, January 06, 2004 4:53 PM
To: '[EMAIL PROTECTED]'
Subject: MySQL 4.0 Installation Problem


I have 3.23 that comes with my Linux distribution, now when I
tried to do a rpm installation of 4.0, I got messages like:
"warning: MySQL-server-4.0.17 ... .rpm: V3 DSA signature: NOKEY,
key ID ...,
file /usr/bin/mysql from install of MySQL-client-4.0.17.0
conflicts with file from package mysql-3.23.52-3
...
file /usr/shar/man/man1/ ... from install of ... conflicts with
file from package mysql-3.23...
..."
and the conflict list goes on.
 
The installation manual does not seem to discuss about such
issues.  Do I need to remove my 3.23 before I run the installation? --
but that's not what the manual says, though.  The first warning msg, is
that a problem, too?
 
Thanks.

Re: MySQL 4.0.x LOAD DATA FROM MASTER wiping out tables...

[Victoria Reznichenko]

Gabriel Ricard <[EMAIL PROTECTED]> wrote:
> I'm running MySQL 4.0.14 on Mac OS X 10.2.6 on a development server. We 
> have around 60 tables on the development server and the production 
> servers. 18 tables that exist on the production server are replicated 
> to our development server. We use the replicate-wild-do-table config 
> option to tell it which tables to replicate from the master (production 
> server) to the slave (dev server).
> 
> Somehow a REPAIR statement on one of the replicated tables failed on 
> the slave recently. It left the .TMD temporary table file, and the .MYD 
> data file disappeared altogether. I did STOP SLAVE; RESET SLAVE; LOAD 
> DATA FROM MASTER; and it reloaded the 18 replicated tables from the 
> production server. However, it also wiped out the other 44 tables that 
> existed on the dev server.
> 
> I looked at the manual page for the LOAD DATA FROM MASTER command 
> (http://www.mysql.com/doc/en/LOAD_DATA_FROM_MASTER.html), and in the 
> first paragraph it states: "Will honor table and database exclusion 
> rules specified with replicate-* options." So, why would it not honor 
> my replicate-wild-do-table configuration and ONLY load those tables? 
> Why would it wipe out everything in the database before doing reloading 
> the replicated tables?
> 

Thanks for the report. It was entered to the bug database as bug #1248:
http://bugs.mysql.com/bug.php?id=1248


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Victoria Reznichenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   <___/   www.mysql.com





-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 Slave to 3.23.55 master Replication

[Egor Egorov]

Devin <[EMAIL PROTECTED]> wrote:
> 
> I noticed that my MySQL 4.0.13 Slave Replication server is having
> a wierd problem. If you look at the master.info file on the slave
> it keeps updating like it is really updating the slave but in
> the mysql.err log it shows:
> 
> 030609 16:12:08  Slave I/O thread: connected to master
> '[EMAIL PROTECTED]:3306',  replication started in log 'io-bin.1964' at
> position 1930590
> ERROR: 1016  Can't open file: 'named.MYI'. (errno: 145)
> 030609 18:34:13  Slave: error 'Can't open file: 'named.MYI'. (errno: 145)'
> on query 'update named set registrar='NETWORK SOLUTIONS, INC.',
> regexpires='2012-06-09', regcreated='', regupdated='2003-02-11',
> whois='\nWhois Server Version 1.3\n\nDomain names in the .com and .net
> domains can now be registered\nwith many different competing registrars.
> Go to http://www.internic.net\nfor detailed information.\n\n   Domain
> Name: HEARTNOTES.COM\n   Registrar: NETWORK SOLUTIONS, INC.\n   Whois
> Server: whois.networksolutions.com\n   Referral URL:
> http://www.networksolutions.com\n   Name Server: NS1.AROS.NET\nFound name
> server NS1.AROS.NET\n   Name Server: NS2.AROS.NET\nFound name server
> NS2.AROS.NET\n   Status: ACTIVE\n   Updated Date: 11-feb-2003\n
> *** Converted 11-feb-2003 into 2003-02-11.\n   Creation Date:
> 10-jun-1998\n   Expiration Date: 09-jun-2012\n   *** Converted
> 09-jun-2012 into 2012-06-09.\n\n\n>>> Last update of whois database: Thu,
> 29 May 2003 17:56:56 EDT <<<\n\nNOTICE: The expiration date displayed in
> this record is the date th', error_code=1016
> 030609 18:34:13  Error running query, slave SQL thread aborted. Fix the
> problem, and restart the slave SQL thread with "SLAVE START". We stopped
> at log 'io-bin.1896' position 7345847
> 
> It complains that it has stopped at position io-bin.1896, position 7345847
> but I can't find how to make it just skip to the next record, any help
> would be appreciated?

$ perror 145
Error code 145:  Unknown error 145
145 = Table was marked as crashed and should be repaired

Your table 'named' is crashed. You need to repair table and then start slave again.



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.0 Installation Problems

[James Marcinek]

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> On Sat, 24 May 2003, Egor Egorov wrote:
>
>> DAVID CLARK <[EMAIL PROTECTED]> wrote:
>> > OK, I messed up. I've been running MySQL 3.23, and I
>> > wanted to upgrade to 4.0 so I could use the new
>> > boolean functions. So I downloaded the 4.0 RPM, and
>> > then tried to install it using -U. I received this
>> > message:
>> >
>> > libmysqlclient.so.10 is needed by (installed)
>> > perl-DBD-MySQL-2.1017-3
>> > libmysqlclient.so.10 is needed by (installed)
>> > php-mysql-4.2.2-8.0.7
>> >
>> > I already had these files in /usr/lib/mysql, so I
>> > tried installing again using --nodeps. Now I can't
>> > connect at all, and I've tried both --oldpackage ing
>> > and -erase ing with no luck. What can I do to either
>> > get 3.23 back and running or get 4.0 working?
>>
>> A dirty trick:
>>
>> 1. Do rpm --upgrade for MySQL-server, MySQL-client,
>>MySQL-devel but not for MySQL-shared.
>> 2. Save /usr/lib/libmysqlclient.so.10* into somewhere
>> 3. Do rpm --erase --force MySQL-shared
>> 4. Do rpm --install MySQL-shared
>> 5. Move saved files back to /usr/lib
>> 6. Run ldconfig as root.
>>
>> In result, you will have the older v10 libs intact for various software.
>
> Or you could simply use the newly added MySQL-shared-compat RPM, that
> already includes both versions of the shared libs...
>
> http://www.mysql.com/doc/en/Linux-RPM.html
>
> Bye,
>   LenZ
> - --
> For technical support contracts, visit https://order.mysql.com/?ref=mlgr
>__  ___ ___   __
>   /  |/  /_ __/ __/ __ \/ /  Mr. Lenz Grimmer <[EMAIL PROTECTED]>
>  / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Production Engineer
> /_/  /_/\_, /___/\___\_\___/ Hamburg, Germany
><___/   www.mysql.com
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
> Comment: For info see http://quantumlab.net/pine_privacy_guard/
>
> iD8DBQE+0woUSVDhKrJykfIRAgkYAJ0VHiRel1eQJOcZ/GxSJvh+1/xGGwCeJBv1
> OespXrFlAM9Nj7nOWQT5Pqw=
> =qm1M
> -END PGP SIGNATURE-
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/[EMAIL PROTECTED]
>


I'm having problems installing certain packages on my RH8 distro. I ended
up using CPAN to install the DBI, CGI and DBD::mysql perl portions. That
solved one set of problems; however, when I try to install the MySQL-MAX
and MySQL-SHARED I get the following errors:

rpm -Uvh MySQL-shared-4.1.0-0.i386.rpm
warning: MySQL-shared-4.1.0-0.i386.rpm: V3 DSA signature: NOKEY, key ID
5072e1f5error: Failed dependencies:
libcrypto.so.0.9.6 is needed by MySQL-shared-4.1.0-0
libssl.so.0.9.6 is needed by MySQL-shared-4.1.0-0

I went to the /lib directory and found libcrypto.so.0.9.6b:

ll libcrypto.so*
-rwxr-xr-x1 root root   983407 Mar 19 15:07 libcrypto.so.0.9.6b
lrwxrwxrwx1 root root   19 May 26 07:04 libcrypto.so.2 ->
libcrypto.so.0.9.6b

The same goes for the libssl:

ll libssl.so*
-rwxr-xr-x1 root root   224733 Mar 19 15:07 libssl.so.0.9.6b
lrwxrwxrwx1 root root   16 May 26 07:04 libssl.so.2 ->
libssl.so.0.9.6b


Is the answer as easy as creating a link to the b files?

Thanks for any help,

James

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

re: MySQL 4.0 and UNICODE

[Egor Egorov]

On Wednesday 26 February 2003 18:49, Juan wrote:

> Does the last binary version available of MySQL
> (4.0xx) support UNICODE?

Unicode will be available since 4.1. There is no binaries for 4.1 yet.



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   <___/   www.mysql.com




-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 and ODBC 3.51

[Roger Baklund]

* Dieter Stelzner
[...]
> I have opened a conection to a MySQL-Server database. How I can get a list
> of all available tables inside the database via ODBC with an SQL
> statement?

Send a "SHOW TABLES" command. Full syntax:

SHOW [OPEN] TABLES [FROM db_name] [LIKE wild]

http://www.mysql.com/doc/en/SHOW.html >

--
Roger


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Mysql 4.0 and ssl

[Brian Leung]

hi all,

i get the following error logdid anyone try to compile mysql with ssl before?

030116 14:34:13  InnoDB: Started
/usr/local/mysql-4.0.9-gamma/libexec/mysqld: ready for connections
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=3997696
read_buffer_size=131072
sort_buffer_size=100
max_used_connections=1
max_connections=1
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 5008 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x866a130
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x41dc8d48, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80de25c
0x40034f05
0x82c9513
0x80e70ad
0x80e7312
0x40031faf
0x420e790a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Res
olved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer
thd->thread_id=3

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 3 did to cause the crash.  In some cases of really
bad corruption, the values shown above may be invalid.

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
030116 14:37:03  mysqld restarted
030116 14:37:04  InnoDB: Started
/usr/local/mysql-4.0.9-gamma/libexec/mysqld: ready for connections
030116 14:45:39  /usr/local/mysql-4.0.9-gamma/libexec/mysqld: Normal shutdown

030116 14:45:39  InnoDB: Starting shutdown...
030116 14:45:40  InnoDB: Shutdown completed
030116 14:45:40  /usr/local/mysql-4.0.9-gamma/libexec/mysqld: Shutdown Complete

Although i set the variables according the above error log, the daemon seems crash
too.

Brian Leung


Brian Leung wrote:

> hi all,
>
> i know some GUI mysql client software can support SSL. Then, i try to
> install mysql 4.0 with |--with-vio --with-openssl| options. i haven't
> install the openssl 0.9.6 again as i found my redhat 7.3 box already has
> the /usr/include/openssl and /usr/lib/libssl.a. After i followed the
> docs in www.mysql.com to grant some people use ssl restriction, i try to
> use the GUI software to connect database. Then,
> the screen print out the following every time when i try to use the GUI
> to connect database. And, finally, the connection is failed.
>
> Number of processes running now: 0
> 030115 20:15:50 mysqld restarted
> Number of processes running now: 0
> 030115 20:15:59 mysqld restarted
> If i don't use SSL, the connection is no problem and no error too. It is
> very strange.
> And, i am so comfuse that the docs in www.mysql.com does not tell you
> about creation of private key and public key. As i know, if you want to
> use SSL, you need to use the key to do encryption and decryption. But,
> the site never mention about this. Why?
>
> Thanks
> Brian
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL-4.0 and PHP with Red Hat 8.0

[Dave Best]

  Your probably better off getting it and compiling it by hand.

Dave
- Original Message -
From: "Florin Andrei" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 30, 2002 4:36 PM
Subject: MySQL-4.0 and PHP with Red Hat 8.0


> Anyone tried to use MySQL-4.0 and the precompiled PHP (the one from the
> distribution packages) in Red Hat 8.0?
> Any problems?
>
> --
> Florin Andrei
>
> Many would-be screenwriters seem to have the impression that they can
> write a script based only on an idea. This is similar to the impression
> that many had during the "dot-com" era that they could get venture
> capital for an idea. (Many did, of course, but that's another story.)
>
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MySQL 4.0 and LIKE "%string%"

[Steven Roussey]

That optimization is for fields without an index AFAIK. 

Sincerely,
Steven Roussey
http://Network54.com/?pp=e 
sql,query



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 stable release

[Thomas Spahni]

On Tue, 27 Aug 2002, Dean Ellis wrote:

> The annoying thing about it, for me, is that MySQL 4.0 has been perfectly 
> stable and perfectly usable for us until 4.0.3, which so far has yet to 
> produce a usable client library.  I keep pulling from CVS and recompiling, 
> hoping that one day soon I'll be able to move beyond 4.0.2.  ;)
> 
> Clients in 4.0.3 simply lock up when they try to access a database (whether a 
> 4.0.2 or 4.0.3 or 3.23 database), for me.  Linux 2.4.19, gcc 3.1.1 and 3.2.

the source tree 4.0.3 works ok for me, but I compiled with gcc 2.95.3

Thomas


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 on Debian

[Tibor Simko]

Hello

On Thu, 1 Aug 2002, Quinten Steenhuis wrote:
> Has anyone successfully gotten MySQL 4.02 running on Debian? I'm
> running into problems if I use alien to convert the RPMs. 

Yep, we're using 4.0.2 on Debian.  You may want to grab MySQL .tar.gz
instead of .rpm and install it somewhere into /usr/local.  Then you
should get no conflicts with whatsoever, and the PHP stuff might Just
Work(TM).  If not, you can try to reconcile new locations of the MySQL
socket file in php.ini or my.cnf files, etc.  (As I'm compiling PHP
myself, I'm not really exactly in your situation.)
 
Tibor

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Re: MySQL 4.0 stable release

[Dean Ellis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 sql,query ...
 On Tuesday 27 August 2002 02:30 pm, walt wrote:
 > There has been some issues with gcc 3.x if I remember correctly. I know
 > RedHat released another beta because of problems with gcc 3.x. Have you
 > tried  it on a box with gcc 2.9x ?

Yes...  I have had identical behavior (the clients lock up immediately upon 
attempting to access a database) with 4.0.3 on two seperate machines, with 
two different Linux distributions and using gcc 2.95, 3.1.1 and 3.2.

As soon as I cloned the 4.0.3 tree, the clients broke.  The server itself is 
fine, and I am, in fact, using the 4.0.2 clients to interact with a 4.0.3 
server without problems.

strace did not provide any useful information, so basically I am not going to 
give it much attention until the "official" 4.0.3 binaries are out.  One way 
or another, they'll help identify the problem.  (Or, if it's a problem with 
MySQL and not, in fact, a problem with, say, my libc or something, I assume 
it will be corrected eventually.)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9a93XRU3T/K5ORe8RAuSeAKCV6yckz9ntdA0xFKCpZhRPxRThQQCfddPm
R3ViGB/QVuyG5sPALhCfNsk=
=H1P2
-END PGP SIGNATURE-

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 stable release

[walt]

Dean Ellis wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tuesday 27 August 2002 11:39 am, Lenz Grimmer wrote:
> > As soon as it actually *is* stable :)
> >
> > On a more serious note, we are currently working on preparing the first
> > release of 4.0  (4.0.3) that will be declared "Beta" instead of "Alpha".
>
> The annoying thing about it, for me, is that MySQL 4.0 has been perfectly
> stable and perfectly usable for us until 4.0.3, which so far has yet to
> produce a usable client library.  I keep pulling from CVS and recompiling,
> hoping that one day soon I'll be able to move beyond 4.0.2.  ;)
>
> Clients in 4.0.3 simply lock up when they try to access a database (whether a
> 4.0.2 or 4.0.3 or 3.23 database), for me.  Linux 2.4.19, gcc 3.1.1 and 3.2.
>
> But it looks like several things were changed for 4.0.3, so I'll wait it out,
> I suppose.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE9a8MwRU3T/K5ORe8RArMOAKCnjNf49O7snEPNvhNJhgrLPTPPsQCeIqKN
> dDUPU2iwJ3bFFZPfOh6cF40=
> =i+W8
> -END PGP SIGNATURE-
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Dean,
There has been some issues with gcc 3.x if I remember correctly. I know RedHat
released another beta because of problems with gcc 3.x. Have you tried  it on a
box with gcc 2.9x ?

walt


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 stable release

[Dean Ellis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 27 August 2002 11:39 am, Lenz Grimmer wrote:
> As soon as it actually *is* stable :)
>
> On a more serious note, we are currently working on preparing the first
> release of 4.0  (4.0.3) that will be declared "Beta" instead of "Alpha".

The annoying thing about it, for me, is that MySQL 4.0 has been perfectly 
stable and perfectly usable for us until 4.0.3, which so far has yet to 
produce a usable client library.  I keep pulling from CVS and recompiling, 
hoping that one day soon I'll be able to move beyond 4.0.2.  ;)

Clients in 4.0.3 simply lock up when they try to access a database (whether a 
4.0.2 or 4.0.3 or 3.23 database), for me.  Linux 2.4.19, gcc 3.1.1 and 3.2.

But it looks like several things were changed for 4.0.3, so I'll wait it out, 
I suppose.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9a8MwRU3T/K5ORe8RArMOAKCnjNf49O7snEPNvhNJhgrLPTPPsQCeIqKN
dDUPU2iwJ3bFFZPfOh6cF40=
=i+W8
-END PGP SIGNATURE-

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 stable release

[Lenz Grimmer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

On Tuesday 27 August 2002 17:17, Scott Pippin wrote:

> When will MySQL 4.0  be released as a stable version?

As soon as it actually *is* stable :)

On a more serious note, we are currently working on preparing the first 
release of 4.0  (4.0.3) that will be declared "Beta" instead of "Alpha". That 
means that we will not add any new features to the 4.0.x code tree anymore, 
but instead focus on fixing the remaining bugs in this release. As soon as 
most bugs have been ironed out and it proves to run stable for most of our 
userbase, it will be declared "gamma" and then "stable".

See http://www.mysql.com/doc/en/Which_version.html for details.

Bye,
LenZ
- -- 
For technical support contracts, visit https://order.mysql.com/?ref=mlgr
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Mr. Lenz Grimmer <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Production Engineer
/_/  /_/\_, /___/\___\_\___/   Hamburg, Germany
   <___/   www.mysql.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9a6s4SVDhKrJykfIRAqbVAJ9t+N6RLGubeMx/nqzY7ORX42HXswCfYVkg
w5QfgrNmRC/hUcwuXF6qsNU=
=JtjI
-END PGP SIGNATURE-


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 stable release

[Jeremy Zawodny]

On Tue, Aug 27, 2002 at 09:17:46AM -0600, Scott Pippin wrote:
> When will MySQL 4.0  be released as a stable version?

Where there have been no reported bugs for a sufficient amount of
time.

Jeremy
-- 
Jeremy D. Zawodny |  Perl, Web, MySQL, Linux Magazine, Yahoo!
<[EMAIL PROTECTED]>  |  http://jeremy.zawodny.com/

MySQL 3.23.51: up 21 days, processed 426,301,880 queries (231/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 on Debian

[Jeremy Zawodny]

On Thu, Aug 01, 2002 at 09:50:33PM -0400, Quinten Steenhuis wrote:
> 
> Hello all,
> 
> Has anyone successfully gotten MySQL 4.02 running on Debian? I'm running
> into problems if I use alien to convert the RPMs. I could install from
> source, but I want to avoid cruftiness and make it easy to upgrade.
> Basically, I run into conflicts with the package libmysqlclient10, but if
> I try to remove this package, I also remove PHP4-mysql, etc.
> 
> If anyone has gotten this to work, what steps have they taken? I
> appreciate debian's update system for Apache and PHP, so I don't want to
> install those from source if it can be avoided. If there's a smarter
> upgrade path, please let me know. I'm willing to try out different ways of
> doing this.

My only suggestion is that you build from source.  What about it do you
find crufty?  I know it's not the "debian way" but there's no .deb
available...

Jeremy
-- 
Jeremy D. Zawodny |  Perl, Web, MySQL, Linux Magazine, Yahoo!
<[EMAIL PROTECTED]>  |  http://jeremy.zawodny.com/

MySQL 3.23.51: up 64 days, processed 1,338,527,626 queries (241/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Jeremy Zawodny]

On Thu, Jun 27, 2002 at 04:21:43PM +0200, Sander Pilon wrote:
> 
> It has not been for us. Replication, query cache and fulltext stuff
> is borked. But, it's an alpha. Alpha's aren't supposed to be stable.

What replication problems have you seen?
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.51: up 28 days, processed 627,309,504 queries (251/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Jocelyn Fournier]

Hi,

I've currently my website and two forum which runs with MySQL 4.0.2
flawlessly (and which a huge number of visitors for one of my forum).

mysql> \s
--
mysql  Ver 12.10 Distrib 4.0.2-alpha, for pc-linux-gnu (i686)

Connection id:  125151
Current database:
Current user:   root@localhost
SSL:Not in use
Current pager:  stdout
Using outfile:  ''
Server version: 4.0.2-alpha-log
Protocol version:   10
Connection: Localhost via UNIX socket
Client characterset:latin1
Server characterset:latin1
UNIX socket:/var/adm/mysql/mysql.sock
Uptime: 4 hours 49 min 50 sec

Threads: 128  Questions: 7734339  Slow queries: 21  Opens: 7113  Flush
tables: 23  Open tables: 262  Queries per second avg: 444.758
--

As you can see, mysql can process a lot of queries/s, without any problem
with the latest 4.0.2 release. (I've just restarted the mysql server on this
example ;))

Regards,
  Jocelyn


- Original Message -
From: "Arul" <[EMAIL PROTECTED]>
To: "MySQL" <[EMAIL PROTECTED]>
Sent: Wednesday, June 26, 2002 4:45 PM
Subject: MYSQL 4.0


> Hi
>
> Any idea when MySQL 4.0 stable release will be made..
> As of now only Alpha is released..
>
> Also any sites which run on 4.0 Alpha
>
> Regards,
> -Arul
>
> To pass the List : sql , query
>
>
>
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
>
>


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Thomas Spahni]

On Thu, 27 Jun 2002, Benjamin Pflugmann wrote:

> On Thu 2002-06-27 at 16:33:43 +0530, [EMAIL PROTECTED] wrote: >

>> But Still Noone have throwed some light on the Date when MySql 4.0
>> Release will be made formally which could enable me to use the Unions
>> Can anyone in this group please let me know...
> 
> Nobody throws in a date, because nobody knows.

Sinisa wrote today:

4.0.2 will be released next week latest.

This is good news!
Thomas


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MYSQL 4.0

[Sander Pilon]

> -Original Message-
> From: Daniel Koch [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, June 27, 2002 13:11
> To: Arul
> Cc: MySQL
> Subject: Re: MYSQL 4.0
> 
> 
> Arul wrote:
> 
> >Hi
> >
> >Any idea when MySQL 4.0 stable release will be made..
> >As of now only Alpha is released..
> >
> >Also any sites which run on 4.0 Alpha
> >
> >  
> >
> 
> 4.0.1 has been very stable for us:
> 

It has not been for us. Replication, query cache and fulltext stuff is
borked. But, it's an alpha. Alpha's aren't supposed to be stable.



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Benjamin Pflugmann]

Hi.

On Thu 2002-06-27 at 16:33:43 +0530, [EMAIL PROTECTED] wrote:
> 
> But Still Noone have throwed some light  on the Date when MySql 4.0 Release
> will be made formally which could enable me to use the Unions
> 
> Can anyone in this group please let me know...

Nobody throws in a date, because nobody knows. The usual answer is
"when it's ready". Altough there is a bigger plan, the developers
generally do prefer to do it Right and not to rush out a release, just
because they have to meet a release date.

That said, 4.0 stable probably can be expected to be released somewhen
within this year.

And as it has been said, it is regarded quite usuable. The "old"
features seem to be stable and for the new ones in 4.0, just install
it and test your uses of it.

> > I am always ready to give a try ..
> > But u see Managers will not be ready to take such a risk...and
> > Morever our client will not give a try ..:((

Well, most problems will not be with stability, but with unexpected
behaviour which should be quite obvious when you encounter it. And as
already has been said, those problem are usually fixed within days
after you report them. More important, those problems will be found in
testing before you go into production phase. So how big would be that
risk, really?

Bye,

Benjamin.


-- 
[EMAIL PROTECTED]

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MYSQL 4.0

[Erlend Hopsø Strømsvik]

Hi

I'm running MySQL 4.0.2 compiled from the source tree on this site:
www.gnist.no (The largest online bookstore in Norway)

Used 4.0.1 earlier but that version had some small problems with fulltext
search.

Server version: 4.0.2-alpha-log
Uptime: 2 days 12 hours 40 min 28 sec
Threads: 13  Questions: 9785444  Slow queries: 66  Opens: 58  Flush tables:
1  Open tables: 38  Queries per second avg: 44.799

Had to shutdown the server to insert a new HD in the RAID. But MySQL has
been working flawlessy the last 2 and 1 half days.


Regards
Erlend Stromsvik


> -Original Message-
> From: Arul [mailto:[EMAIL PROTECTED]]
> Sent: 26. juni 2002 16:45
> To: MySQL
> Subject: MYSQL 4.0
> 
> 
> Hi 
> 
> Any idea when MySQL 4.0 stable release will be made..
> As of now only Alpha is released..
> 
> Also any sites which run on 4.0 Alpha
> 
> Regards,
> -Arul
> 
> To pass the List : sql , query
> 

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Gerald Jensen]

Sad ... we gave MySQL a try almost three years ago, wound up replacing M$'s
SQL Server with MySQL, and now have 80+ very happy customers with a stable,
powerful, and very cost-effective database solution.

- Original Message -
From: "Arul" <[EMAIL PROTECTED]>
To: "Thomas Spahni" <[EMAIL PROTECTED]>
Cc: "MySQL" <[EMAIL PROTECTED]>
Sent: Thursday, June 27, 2002 3:42 AM
Subject: Re: MYSQL 4.0


> Hi Thomas
>
> I am always ready to give a try ..
> But u see Managers will not be ready to take such a risk...and Morever our
> client will not give a try ..:((
>
> -Arul
>
>
> - Original Message -
> From: "Thomas Spahni" <[EMAIL PROTECTED]>
> To: "Arul" <[EMAIL PROTECTED]>
> Cc: "MySQL" <[EMAIL PROTECTED]>
> Sent: Thursday, June 27, 2002 1:27 PM
> Subject: Re: MYSQL 4.0
>
>
> > Arul,
> >
> > as you are intending to use open source software for free why not give
it
> > a try and help with debugging?
> >
> > 4.0.1 is remarkably stable except for some glitches in replication and
> > boolean fulltext search. Alpha status applies mainly to the newly
> > developed features.
> >
> > Go ahead and have fun!
> > Thomas
> >
> > On Wed, 26 Jun 2002, Arul wrote:
> >
> > > Hi
> > >
> > > Any idea when MySQL 4.0 stable release will be made..
> > > As of now only Alpha is released..
> > >
> > > Also any sites which run on 4.0 Alpha
> > >
> > > Regards,
> > > -Arul
> > >
> > > To pass the List : sql , query
> >
>
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
>


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Daniel Koch]

Arul wrote:

>Hi 
>
>Any idea when MySQL 4.0 stable release will be made..
>As of now only Alpha is released..
>
>Also any sites which run on 4.0 Alpha
>
>  
>

4.0.1 has been very stable for us:


[root@db1 root]# mysqladmin version
mysqladmin  Ver 8.23 Distrib 4.0.1-alpha, for pc-linux-gnu on i686
Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license

Server version  4.0.1-alpha-Max
Protocol version10
Connection  Localhost via UNIX socket
UNIX socket /var/lib/mysql/mysql.sock
Uptime: 71 days 4 hours 13 min 6 sec

Threads: 93  Questions: 462031153  Slow queries: 5680  Opens: 28001  
Flush table
s: 143  Open tables: 132  Queries per second avg: 75.132





-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Arul]

Hi

But Still Noone have throwed some light  on the Date when MySql 4.0 Release
will be made formally which could enable me to use the Unions

Can anyone in this group please let me know...

-Arul
- Original Message -
From: "Arul" <[EMAIL PROTECTED]>
To: "Thomas Spahni" <[EMAIL PROTECTED]>
Cc: "MySQL" <[EMAIL PROTECTED]>
Sent: Thursday, June 27, 2002 2:12 PM
Subject: Re: MYSQL 4.0


> Hi Thomas
>
> I am always ready to give a try ..
> But u see Managers will not be ready to take such a risk...and Morever our
> client will not give a try ..:((
>
> -Arul
>
>
> - Original Message -
> From: "Thomas Spahni" <[EMAIL PROTECTED]>
> To: "Arul" <[EMAIL PROTECTED]>
> Cc: "MySQL" <[EMAIL PROTECTED]>
> Sent: Thursday, June 27, 2002 1:27 PM
> Subject: Re: MYSQL 4.0
>
>
> > Arul,
> >
> > as you are intending to use open source software for free why not give
it
> > a try and help with debugging?
> >
> > 4.0.1 is remarkably stable except for some glitches in replication and
> > boolean fulltext search. Alpha status applies mainly to the newly
> > developed features.
> >
> > Go ahead and have fun!
> > Thomas
> >
> > On Wed, 26 Jun 2002, Arul wrote:
> >
> > > Hi
> > >
> > > Any idea when MySQL 4.0 stable release will be made..
> > > As of now only Alpha is released..
> > >
> > > Also any sites which run on 4.0 Alpha
> > >
> > > Regards,
> > > -Arul
> > >
> > > To pass the List : sql , query
> >
>
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Arul]

Hi Thomas

I am always ready to give a try ..
But u see Managers will not be ready to take such a risk...and Morever our
client will not give a try ..:((

-Arul


- Original Message -
From: "Thomas Spahni" <[EMAIL PROTECTED]>
To: "Arul" <[EMAIL PROTECTED]>
Cc: "MySQL" <[EMAIL PROTECTED]>
Sent: Thursday, June 27, 2002 1:27 PM
Subject: Re: MYSQL 4.0


> Arul,
>
> as you are intending to use open source software for free why not give it
> a try and help with debugging?
>
> 4.0.1 is remarkably stable except for some glitches in replication and
> boolean fulltext search. Alpha status applies mainly to the newly
> developed features.
>
> Go ahead and have fun!
> Thomas
>
> On Wed, 26 Jun 2002, Arul wrote:
>
> > Hi
> >
> > Any idea when MySQL 4.0 stable release will be made..
> > As of now only Alpha is released..
> >
> > Also any sites which run on 4.0 Alpha
> >
> > Regards,
> > -Arul
> >
> > To pass the List : sql , query
>


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Thomas Spahni]

Arul,

as you are intending to use open source software for free why not give it
a try and help with debugging?

4.0.1 is remarkably stable except for some glitches in replication and
boolean fulltext search. Alpha status applies mainly to the newly
developed features.

Go ahead and have fun!
Thomas

On Wed, 26 Jun 2002, Arul wrote:

> Hi 
> 
> Any idea when MySQL 4.0 stable release will be made..
> As of now only Alpha is released..
> 
> Also any sites which run on 4.0 Alpha
> 
> Regards,
> -Arul
> 
> To pass the List : sql , query


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Jeremy Zawodny]

On Thu, Jun 27, 2002 at 05:27:29PM +0930, G r e g   L a w r i e wrote:
> Jeremy,
> 
> Would you mind sharing how many machines 'half your servers' might
> be, what type of work are they doing and how long have they been up
> for / how stable would you consider them to be?

Half of "my" server is, uhm, 3 right now.  We're planning to do some
upgrades and machine swaps on the east cost shortly.  After that
happens, we'll have couple more.

(Once we've proven it in our group, I know of many others that will
probably follow suit within a couple months.)

So far, I'm only upgrading the slaves, but I expect to do the master
in a month or so.  Probably after the Open Source Convention.  If I
upgrade it and then leave town, it *will* break.

Here's a mytop snipit from one of the boxes:

MySQL on db3.finance.sc5 (4.0.2-alpha-log)up 5+16:21:27 [01:11:10]
 Queries Total: 41,747,472 Avg/Sec: 85.04  Slow: 8
 Threads Total: 1 Active: 1 Cached: 0
 Key Efficiency: 99.43%  Bytes in: 1,710,858,529  Bytes out: 495,705,494

It has been up for 5 days because I recently updated the code.  I
wanted to put a newer 4.0.2-alpha snapshot on it.  Before that it had
been up for a few weeks and had probably run 150-200 million queries.
It's pretty lightly loaded now.  But it'll become our new master in a
month or so.

Other than the InnoDB bug we discovered, stability is not an issue.
That was fixed within 36 hours of the diagnosis.  I should point out
that we're really not using any of the whiz-bang new 4.0.x features
(other than the revamped replication).  But for 3.23.xx style work, it
has treated us well so far.

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.51: up 28 days, processed 614,127,052 queries (250/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MYSQL 4.0

[G r e g L a w r i e]

Jeremy,

Would you mind sharing how many machines 'half your servers' might be, what
type of work are they doing and how long have they been up for / how stable
would you consider them to be?

Thanks,

Greg


-Original Message-
From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 27 June 2002 16:23
To: Arul
Cc: MySQL
Subject: Re: MYSQL 4.0


On Wed, Jun 26, 2002 at 08:15:11PM +0530, Arul wrote:
> Hi
>
> Any idea when MySQL 4.0 stable release will be made..
> As of now only Alpha is released..

Rumor has it that 4.0.2 might be beta.

> Also any sites which run on 4.0 Alpha

Yes.  Half my servers have been moved to what will be 4.0.2.
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.51: up 28 days, processed 612,154,047 queries (250/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0

[Jeremy Zawodny]

On Wed, Jun 26, 2002 at 08:15:11PM +0530, Arul wrote:
> Hi 
> 
> Any idea when MySQL 4.0 stable release will be made..
> As of now only Alpha is released..

Rumor has it that 4.0.2 might be beta.

> Also any sites which run on 4.0 Alpha

Yes.  Half my servers have been moved to what will be 4.0.2.
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.51: up 28 days, processed 612,154,047 queries (250/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Mysql 4.0.x enough stable to be in production ?

[Anthony W. Marino]

What table types are you using?

Anthony

> I've been running 4.0.1-alpha on a development server for our new internet
> bookstore. Holds around 1.3million books, 100k bookcovers and a lot of
> other information.
>
> I haven't experienced any crash/problems except for one bug that brings
> down MySQL: using two 'match-against' in fulltext search with some words
> will shutdown mysql.
> Not sure if it's already fixed or not, but if I get some free time later
> this week I'll try to make a test case for the mysql-team.
>
> But anyway, not counting that bug I haven't experienced any problems. But
> alpha is alpha... :p
>
> Since the logistics etc. are stored on a different server I wouldn't have
> any problems using this server as our main web-server (which is what I'm
> going to do in 3 weeks). Restoring the whole server from total crash is
> relativly easy, so a mysql bug wouldn't hurt much anyway
>
>
> Regards
> Erlend Stromsvik
>
> - Original Message -
> From: "David BORDAS" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, April 23, 2002 9:09 AM
> Subject: Mysql 4.0.x enough stable to be in production ?
>
> > Hi all,
> >
> > just one question, i need to use an index on a specific query.
> > This feature in fact :
> > http://www.mysql.com/doc/N/e/News-4.0.0.html
> > << ORDER BY ... DESC can now use keys.  >>
> >
> > And this one is only available in mysql 4.0.x.
> >
> > I'll give a try to mysql 4.0 in a test server.
> >
> > But i need some feed back, did someone using mysql 4.0.x in production ?
> >
> > I know it's an alpha release :(
> >
> > Thanks
> > David
> >
> >
> > -
> > Before posting, please check:
> >http://www.mysql.com/manual.php   (the manual)
> >http://lists.mysql.com/   (the list archive)
> >
> > To request this thread, e-mail <[EMAIL PROTECTED]>
> > To unsubscribe, e-mail <[EMAIL PROTECTED]>
> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
> <[EMAIL PROTECTED]> Trouble
> unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-- 
Anthony W. Marino
Pres./CTO, AWM Objects
email:  [EMAIL PROTECTED]
phone:  (732) 610-2441


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Mysql 4.0.x enough stable to be in production ?

[Erlend Stromsvik]

I've been running 4.0.1-alpha on a development server for our new internet
bookstore. Holds around 1.3million books, 100k bookcovers and a lot of other
information.

I haven't experienced any crash/problems except for one bug that brings down
MySQL: using two 'match-against' in fulltext search with some words will
shutdown mysql.
Not sure if it's already fixed or not, but if I get some free time later
this week I'll try to make a test case for the mysql-team.

But anyway, not counting that bug I haven't experienced any problems. But
alpha is alpha... :p

Since the logistics etc. are stored on a different server I wouldn't have
any problems using this server as our main web-server (which is what I'm
going to do in 3 weeks). Restoring the whole server from total crash is
relativly easy, so a mysql bug wouldn't hurt much anyway


Regards
Erlend Stromsvik

- Original Message -
From: "David BORDAS" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 23, 2002 9:09 AM
Subject: Mysql 4.0.x enough stable to be in production ?


> Hi all,
>
> just one question, i need to use an index on a specific query.
> This feature in fact :
> http://www.mysql.com/doc/N/e/News-4.0.0.html
> << ORDER BY ... DESC can now use keys.  >>
>
> And this one is only available in mysql 4.0.x.
>
> I'll give a try to mysql 4.0 in a test server.
>
> But i need some feed back, did someone using mysql 4.0.x in production ?
>
> I know it's an alpha release :(
>
> Thanks
> David
>
>
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0 Beta

[Jeremy Zawodny]

On Thu, Apr 11, 2002 at 07:16:34AM -0700, va ku wrote:
> Hi,
> 
> We want to use only MYSQL4.0 for our production database.  Please
> let us know when the Beta release is scheduled.

When it's ready. :-)

Seriously, check the archives.  This comes up a lot and the answer is
nearly always the same.

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 63 days, processed 1,712,129,532 queries (312/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Jeremy Zawodny]

On Sat, Mar 09, 2002 at 01:21:44PM -0700, Sasha Pachev wrote:
> On Saturday 09 March 2002 12:46 pm, Jeremy Zawodny wrote:
> > That reminds me of an easy feature request. ?Would it be possible to
> > have a slave-auto-start=no option (or something like that) in my.cnf?
> > There have been cases when I want to start a server but do not want
> > replication to start on its own?
> 
> Already there - --skip-slave-start.

Ah!  It's amazing how I can look right past something when I'm already
sure I know what I'm looking for..

*sigh*

Thanks.
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 30 days, processed 1,025,808,589 queries (392/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Sasha Pachev]

On Saturday 09 March 2002 12:46 pm, Jeremy Zawodny wrote:
> That reminds me of an easy feature request. ?Would it be possible to
> have a slave-auto-start=no option (or something like that) in my.cnf?
> There have been cases when I want to start a server but do not want
> replication to start on its own?

Already there - --skip-slave-start.

-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___ ___   __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
   <___/  

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Jeremy Zawodny]

On Sat, Mar 09, 2002 at 12:31:20PM -0700, Sasha Pachev wrote:
> 
> Jeremy:
> 
> I think I now understand what happened, or at least I have a
> pausilble theory that explains what I see in the logs.
> 
> When I had you kill the broken mysqld last time it went down in the
> middle of updating db3-relay-bin.005 - that is the only explanation
> I can think of for it being truncated in the middle of event and
> especially at such a strange position that is not anywhere near your
> max_binlog_size value.

That does make sense, yes.

That reminds me of an easy feature request.  Would it be possible to
have a slave-auto-start=no option (or something like that) in my.cnf?
There have been cases when I want to start a server but do not want
replication to start on its own?

> To prove this, check modification time on db3-relay-bin.005 - should
> be around the time mysqld was killed and should be almost identical
> to the creation time on the first core, if you still have it around.

Actually, I blew away the core file just a few hours ago.  And the
relay-bin file has been processed and is gone now. :-(

> Nevertheless, it was a blessing in disguise to have the stale broken
> log laying around - it helped me find a different bug.

Excellent.

> However, we need to fix the stale log problem before we can go
> on. One way to do is to re-start the whole replication from
> scratch. A more creative way would be to use dd to trim
> db3-relay-bin.005 down to 214929332 bytes and re-start the server.

The server is well past that point already with the new code, so I
guess that won't be necessary.

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 30 days, processed 1,024,823,330 queries (392/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Sasha Pachev]

On Thursday 07 March 2002 10:48 pm, Jeremy Zawodny wrote:
> The 4.0.x slave I had just rebuilt the other day died about 40 minutes
> ago and produced a core file each time. ?It got caught in the cycle of
> "core dump, restart, core dump, restart..."

Jeremy:

I think I now understand what happened, or at least I have a pausilble theory 
that explains what I see in the logs.

When I had you kill the broken mysqld last time it went down in the middle of 
updating db3-relay-bin.005 - that is the only explanation I can think of for 
it being truncated in the middle of event and especially at such a strange 
position that is not anywhere near your max_binlog_size value. To prove this, 
check modification time on db3-relay-bin.005 - should be around the time 
mysqld was killed and should be almost identical to the creation time on the 
first core, if you still have it around.

Nevertheless, it was a blessing in disguise to have the stale broken log 
laying around - it helped me find a different bug. However, we need to fix 
the stale log problem before we can go on. One way to do is to re-start the 
whole replication from scratch. A more creative way would be to use dd to 
trim db3-relay-bin.005 down to 214929332 bytes and re-start the server.

-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___ ___   __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
   <___/  

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Jeremy Zawodny]

On Fri, Mar 08, 2002 at 05:10:02PM -0800, Jeremy Zawodny wrote:
> > 
> > I have tracked down and fixed the assertion failure issue. However,
> > I am still not certail why the sql thread does partial reads. I have
> > pushed my fix into the public tree, so let's have you pull it and
> > try again.
> 
> Yeah, I just saw that.  I'll rebuild and let it run.

The new code is up and running well.  Interestingly, the very slow
SHOW SLAVE STATUS problems seem to have diminished.  The longest I've
waited for one of those is about 4-5 seconds.  That's down from 25-30
seconds with the previous version I had built.  Don't know if you
changes would have impacted that or not.

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 29 days, processed 1,016,694,208 queries (397/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Jeremy Zawodny]

On Fri, Mar 08, 2002 at 03:14:31PM -0700, Sasha Pachev wrote:
> On Thursday 07 March 2002 10:48 pm, Jeremy Zawodny wrote:
> > The 4.0.x slave I had just rebuilt the other day died about 40 minutes
> > ago and produced a core file each time. ?It got caught in the cycle of
> > "core dump, restart, core dump, restart..."
> 
> Jeremy:
> 
> I have tracked down and fixed the assertion failure issue. However,
> I am still not certail why the sql thread does partial reads. I have
> pushed my fix into the public tree, so let's have you pull it and
> try again.

Yeah, I just saw that.  I'll rebuild and let it run.

> I am curious to see :
> 
>  a) if re-try after the failed read will actually do any good
>  b) why the read is failing in the first place

Right.

> if a) does not do any good the daemon will be stuck trying to read
> the same event, but will not generate assertion failure. b) could be
> happening because of some system failure, or it could be a logic
> error. In any case, I would like to have a look at
> db3-relay-bin.005.

You'll find db3-relay-bin.005.gz uploaded in the secret directory on
your support FTP server.  Once completely uploaded, it's about 29MB in
size.

Thanks!

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 29 days, processed 1,015,158,099 queries (398/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Sasha Pachev]

On Thursday 07 March 2002 10:48 pm, Jeremy Zawodny wrote:
> The 4.0.x slave I had just rebuilt the other day died about 40 minutes
> ago and produced a core file each time. ?It got caught in the cycle of
> "core dump, restart, core dump, restart..."

Jeremy:

I have tracked down and fixed the assertion failure issue. However, I am 
still not certail why the sql thread does partial reads. I have pushed my fix 
into the public tree, so let's have you pull it and try again. I am curious 
to see :

 a) if re-try after the failed read will actually do any good
 b) why the read is failing in the first place

if a) does not do any good the daemon will be stuck trying to read the same 
event, but will not generate assertion failure. b) could be happening because 
of some system failure, or it could be a logic error. In any case, I would 
like to have a look at db3-relay-bin.005.
 
-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___ ___   __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
   <___/  

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Jeremy Zawodny]

On Fri, Mar 08, 2002 at 10:41:32AM -0700, Sasha Pachev wrote:
> On Thursday 07 March 2002 11:39 pm, Jeremy Zawodny wrote:
> > 020307 21:39:03 ?Error in Log_event::read_log_event(): 'read error', 
> data_len=193,event_type=2
> > 020307 21:39:03 ?Slave SQL thread: I/O error reading 
> event(errno=-1,cur_log->error=57)
> > assertion "mi->io_thd == thd" failed: file "slave.cc", line 610
> 
> Jeremy:
> 
> Looks like we've got several things cooking. Somehow the read by the
> SQL thread from the relay log was incomplete ( possibly some I/O
> issues in the kernel?), and at the same time apparently some buffer
> overrun took place. Can you upload the core file + the binary to our
> secret locatioin?

Sasha,

For some reason I can't get your FTP server to like me.  Does it not
like passive connections or something?

Anyway, can you download the mysqld.gz and mysqld.core.1.gz from here?

  http://db3.finance.dcx.yahoo.com/tmp/

They compressed pretty well.

Oh, this is a 4.3 FreeBSD system.

Thanks,

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 29 days, processed 1,011,945,786 queries (400/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Sasha Pachev]

On Thursday 07 March 2002 11:39 pm, Jeremy Zawodny wrote:
> 020307 21:39:03 ?Error in Log_event::read_log_event(): 'read error', 
data_len=193,event_type=2
> 020307 21:39:03 ?Slave SQL thread: I/O error reading 
event(errno=-1,cur_log->error=57)
> assertion "mi->io_thd == thd" failed: file "slave.cc", line 610

Jeremy:

Looks like we've got several things cooking. Somehow the read by the SQL 
thread from the relay log was incomplete ( possibly some I/O issues in the 
kernel?), and at the same time apparently some buffer overrun took place. Can 
you upload the core file + the binary to our secret locatioin?

-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___ ___   __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
   <___/  

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0.x Replication Just Dumped Core...

[Jeremy Zawodny]

On Thu, Mar 07, 2002 at 09:48:41PM -0800, Jeremy Zawodny wrote:
> Hey Sasha,

[snip]

> I'll keep it off-line until I hear from you on what data you need.

Oops.  Here's the info form the error log:

---snip---

020307 21:39:03  Slave I/O thread initialized
020307 21:39:03  Slave SQL thread initialized, starting replication in log 
'binary-log.047' at position 519734079,relay log: 
name='./db3-relay-bin.005',pos='214929332'
020307 21:39:03  Error in Log_event::read_log_event(): 'read error', 
data_len=193,event_type=2
020307 21:39:03  Slave SQL thread: I/O error reading event(errno=-1,cur_log->error=57)
assertion "mi->io_thd == thd" failed: file "slave.cc", line 610
020307 21:39:20  mysqld restarted
Warning: One can only use the --user switch if running as root
/home/mysql-4-bk/libexec/mysqld: ready for connections
020307 21:39:23  Slave I/O thread initialized
020307 21:39:23  Slave SQL thread initialized, starting replication in log 
'binary-log.047' at position 519734079,relay log: 
name='./db3-relay-bin.005',pos='214929332'
020307 21:39:23  Error in Log_event::read_log_event(): 'read error', 
data_len=193,event_type=2
020307 21:39:23  Slave SQL thread: I/O error reading event(errno=-1,cur_log->error=57)
assertion "mi->io_thd == thd" failed: file "slave.cc", line 610
020307 21:39:40  mysqld restarted
Warning: One can only use the --user switch if running as root
/home/mysql-4-bk/libexec/mysqld: ready for connections
020307 21:39:43  Slave I/O thread initialized
020307 21:39:43  Slave SQL thread initialized, starting replication in log 
'binary-log.047' at position 519734079,relay log: 
name='./db3-relay-bin.005',pos='214929332'
020307 21:39:43  Error in Log_event::read_log_event(): 'read error', 
data_len=193,event_type=2
020307 21:39:43  Slave SQL thread: I/O error reading event(errno=-1,cur_log->error=57)
assertion "mi->io_thd == thd" failed: file "slave.cc", line 610
020307 21:40:00  mysqld restarted
Warning: One can only use the --user switch if running as root
/home/mysql-4-bk/libexec/mysqld: ready for connections
020307 21:40:03  Slave I/O thread initialized
020307 21:40:03  Slave SQL thread initialized, starting replication in log 
'binary-log.047' at position 519734079,relay log: 
name='./db3-relay-bin.005',pos='214929332'
020307 21:40:03  Error in Log_event::read_log_event(): 'read error', 
data_len=193,event_type=2
020307 21:40:03  Slave SQL thread: I/O error reading event(errno=-1,cur_log->error=57)
assertion "mi->io_thd == thd" failed: file "slave.cc", line 610

---snip---

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 28 days, processed 1,003,176,241 queries (404/sec. avg)

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Mysql 4.0 or 3.23 with innodb?

[Trond Eivind Glomsrød]

Varshavchick Alexander <[EMAIL PROTECTED]> writes:

> Gentlemen,
> 
> Can you advice please if I'd wish to change the database format from
> myisam to innodb should I upgrade to mysql 4.0 to get better performance
> and stability, or switching to innodb alone under 3.23 will do the
> trick?

Switching to 4.0 for stability doesn't seem like a good idea - it's
still in development, and classified as "alpha". The 3.23 series has
been around a lot longer, and is stable.
 

-- 
Trond Eivind Glomsrød
Red Hat, Inc.

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 released

[Michael Widenius]

Hi!

First, please don't email things directly to me or to the announce
list.  The best way to get help for a problem, is to write an email
only to [EMAIL PROTECTED];  In the future, please also change the
subject line to something that is appropriate and don't respond to an
email that has nothing to do with the problem!

> "Huang-Ming" == Huang-Ming  <[EMAIL PROTECTED]> writes:

Huang-Ming> Hello,
Huang-Ming> I'm encountering a serious program fault at using MySQL Win32 client 
library
Huang-Ming> LIBMYSQL.DLL.

Huang-Ming> I found LIBMYSQL.DLL not thread-safe. When 10 threads are launched to run
Huang-Ming> the following two blocks of C statements, very quickly a program fault
Huang-Ming> window pops up to LIBMYSQL.DLL.

Huang-Ming>  block #1 -
Huang-Ming> EnterCriticalSection(&dcs);
Huang-Ming> mysql_real_query(db,stmt,strlen(stmt));
Huang-Ming> res=mysql_store_result(db);
Huang-Ming> LeaveCriticalSection(&dcs);

Huang-Ming>  block #1 - (in another C function)
Huang-Ming> EnterCriticalSection(&dcs);
Huang-Ming> row=mysql_fetch_row(res);
Huang-Ming> nfld=mysql_num_fields(res);
Huang-Ming> flds=mysql_fetch_fields(res);
Huang-Ming> LeaveCriticalSection(&dcs);

If this block is done by another thread that did the original query,
you will get a problem if you didn't initialize the thread for MySQL
usage.

Please read the MySQL manual section 'Threaded clients' and the
documentation for the MySQL API 'mysql_thread_init()' or more
information about this

Regards,
Monty

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 released

[Huang-Ming]

Hello,

I'm encountering a serious program fault at using MySQL Win32 client library
LIBMYSQL.DLL.

I found LIBMYSQL.DLL not thread-safe. When 10 threads are launched to run
the following two blocks of C statements, very quickly a program fault
window pops up to LIBMYSQL.DLL.

 block #1 -
EnterCriticalSection(&dcs);
mysql_real_query(db,stmt,strlen(stmt));
res=mysql_store_result(db);
LeaveCriticalSection(&dcs);

 block #1 - (in another C function)
EnterCriticalSection(&dcs);
row=mysql_fetch_row(res);
nfld=mysql_num_fields(res);
flds=mysql_fetch_fields(res);
LeaveCriticalSection(&dcs);

But, if I merged the two blocks into one as:

EnterCriticalSection(&dcs);
mysql_real_query(db,stmt,strlen(stmt));
res=mysql_store_result(db);
row=mysql_fetch_row(res);
nfld=mysql_num_fields(res);
flds=mysql_fetch_fields(res);
LeaveCriticalSection(&dcs);

then, the threads run fine for hours without any program fault pop up.

HOWEVER, the second scenario is irrelevant to my (and most multithreaded)
application where there are many nested queries of rows.

Is there any thread-safe LIBMYSQL.DLL downloadable on mysql.com?? or is
there any other solution to make SQL queries by simultaneous threads safe?

Thank You!

Best Regards,
Peter

- Original Message -
From: Michael Widenius <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, October 16, 2001 6:29 AM
Subject: MySQL 4.0 released


>
> Hi!
>
> MySQL 4.0.0-alpha is now available at:
> http://www.mysql.com/downloads/mysql-4.0.html
>
> You can find information about upgrading from MySQL 3.23 to 4.0 at:
> http://www.mysql.com/doc/U/p/Upgrading-from-3.23.html
>
> The MySQL 4.0 release includes a lot of new exciting features, like
> MySQL as an embedded library, InnoDB (transactions) as standard table
> type, UNION, multi table delete and much more.
>
> MySQL 4.0 is basically a 'reconstruction release' that will enable us to
> easier add new features to MySQL in the future.  The intention is to
> quickly add features list at:
>
> http://www.mysql.com/doc/T/O/TODO_MySQL_4.0.html
>
> and then start to work on the 4.1 branch while 4.0 stabilizes.
>
> Changes in release 4.0.0
> 
>
>* Added documentation for `libmysqld', the embedded MySQL server
>  library.  Also added example programs (a `mysql' client and
>  `mysqltest' test program) which use `libmysqld'.
>
>* Removed all Gemini hooks from MySQL.
>
>* Removed `my_thread_init()' and `my_thread_end()' from mysql_com.h,
>  and added `mysql_thread_init()' and `mysql_thread_end()' to
>  mysql.h.
>
>* Secure connections (with SSL).
>
>* Unsigned `BIGINT' constants now work. `MIN()' and `MAX()' now
>  handles signed and unsigned `BIGINT' numbers correctly.
>
>* New character set `latin_de' which provides correct German sorting.
>
>* `TRUNCATE TABLE' and `DELETE FROM table_name' are now separate
>  functions. One bonus is that `DELETE FROM table_name' now returns
>  the number of deleted rows.
>
>* `DROP DATABASE' now executes a `DROP TABLE' on all tables in the
>  database, which fixes a problem with InnoDB tables.
>
>* Added support for `UNION'.
>
>* A new `HANDLER' interface to `MyISAM' tables.
>
>* Added support for `INSERT' on `MERGE' tables. Patch from Benjamin
>  Pflugmann.
>
>* Changed `WEEK(#,0)' to match the calender in the USA.
>
>* `COUNT(DISTINCT)' is about 30% faster.
>
>* Speed up all internal list handling.
>
>* Speed up `IS NULL()' and some other internal primitives.
>
>* Creating full text indexes are now much faster.
>
>* Tree-like cache to speed up bulk inserts and
>  `myisam_bulk_insert_tree_size' variable.
>
>* Searching on packed (`CHAR'/`VARCHAR') keys are now much faster.
>
>* Optimized queries of type: `SELECT DISTINCT * from table_name
>  ORDER by key_part1 LIMIT #'
>
>* `SHOW CREATE TABLE' now shows all table attributes.
>
>* `ORDER BY ... DESC' can now use keys.
>
>* `LOAD DATA FROM MASTER' "auto-magically" sets up a slave.
>
>* Renamed `safe_mysqld' to `mysqld_safe'.
>
>* Added support for symbolic links to `MyISAM' tables. Symlink
>  handling is now enabled by default for Windows.
>
>* `LOAD DATA FROM MASTER' "auto-magically" sets up a slave.
>
>* Added `SQL_CALC_FOUND_ROWS' and `FOUND_ROWS()'. This makes it
>  possible to know how many rows a query would have returned without
>  a `LIMIT' clause.
>
>* Changed output format of `SHOW OPEN TABLES'.
>
>* Allow `SELECT expression LIMIT ...'.
>
>* Added `IDENTITY' as a synonym for `AUTO_INCREMENT' (like Sybase).
>
>* Added `ORDER BY' syntax to `UPDATE' and `DELETE'.
>
>* `SHOW INDEXES' is now a synonym for `SHOW INDEX'.
>
>* Added `ALTER TABLE table_name DISABLE KEYS' and `ALTER TABLE
>  table_name ENABLE KEYS' commands.
>
>* Allow 

Re: Mysql 4.0

[Tor R. Skoglund (NextG)]

Hi, glad to hear that it is not only me...

I got the same error on Pentium 200MMX, even when compiling the
source. I found that configure prepared gcc for Pentium Pro, so the quick
and dirty
fix was to hardcode Pentium into the configure script.
This must be a bug...

Tor Rune Skoglund,  Gyldenløves gt. 4, 7014 Trondheim, Norway
Tlf: 7354 0375 (j)


- Original Message -
From: "Harald Fuchs" <[EMAIL PROTECTED]>


> In article ,
> Robert Alexander <[EMAIL PROTECTED]> writes:
>
> > I'm getting the exact same error when trying to install MySQL 4.0 on
RedHat 7.0 -- both the binary distribution and the RPM.
> > Previous binary versions of MySQL have worked just fine on the same
machine.
>
> It seems to depend on the CPU.  For me the binary distribution of
> MySQL 4.0 works fine on Pentiums and Athlons, but I get illegal
> instructions on K6/2s.




-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Mysql 4.0

[Matt Wagner]

Harald Fuchs writes:
> In article ,
> Robert Alexander <[EMAIL PROTECTED]> writes:
> 
> > I'm getting the exact same error when trying to install MySQL 4.0 on RedHat 7.0 -- 
>both the binary distribution and the RPM.
> > Previous binary versions of MySQL have worked just fine on the same machine.
> 
> It seems to depend on the CPU.  For me the binary distribution of
> MySQL 4.0 works fine on Pentiums and Athlons, but I get illegal
> instructions on K6/2s.

Hi,

AFAIK, this should be fixed when 4.0.1 comes out in a couple days.


Matt

-- 
For technical support contracts, visit https://order.mysql.com/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Mr. Matt Wagner <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Herr Direktor
/_/  /_/\_, /___/\___\_\___/   Hopkins, Minnesota  USA
   <___/   www.mysql.com

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Mysql 4.0

[Robert Alexander]

I'm getting the exact same error when trying to install MySQL 4.0 on RedHat 7.0 -- 
both the binary distribution and the RPM.

Previous binary versions of MySQL have worked just fine on the same machine.

/Rob


At 10:07 -0800 2001/12/06, em huynh wrote:
>I also tried using the binary distribution. and get the following error
>when trying to start
>
>Starting mysqld daemon with databases from /usr/local/mysql/data
>/usr/local/mysql/bin/mysqld_safe: line 278:  9578 Illegal instruction
>$NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION
>--datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking
>>>$err_log 2>&1
>011206 02:51:49  mysqld ended


~
Robert Alexander, Alpha Geek, Workmate.ca
WWW Database Applications and Web Hosting
http://www.workmate.ca   416-823-6599
mailto:[EMAIL PROTECTED]

"Life's unfair - but root password helps!"

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 fulltext search truncation bug?

[Sergei Golubchik]

Hi!

On Nov 26, sherzodR wrote:
> 
> 
> Use "%" instead of "*"
> 
> cheers
> --
> sherzodR
> 
> 
> On 26 Nov 2001, Harald Fuchs wrote:
> 
> >According to the manual, section "New Features of Full-text Search to
> >Appear in MySQL 4.0":
> >
> >* `*' is a truncation operator.
> >
> >The query
> >  SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versailles')
> >returns 2, but
> >  SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versaill*')
> >returns 0  on MySQL 4.0.
> >
> >Is this a bug, or do I misunderstand the meaning of "truncation"?

First - no, according to the manual '*' is a truncation operator, not
'%', so your syntax is correct.

Second - probably it's a bug. I cannot say much as the code used by this
query was removed from MySQL source tree. It was replaced by completely
new boolean search engine written from scratch. Unfortunately it was
done several days _after_ 4.0.0 release.

Wait for 4.0.1 - it should be out in a few days.

Regards,
Sergei

-- 
MySQL Development Team
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Osnabrueck, Germany
   <___/

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 fulltext search truncation bug?

[sherzodR]

Use "%" instead of "*"

cheers
--
sherzodR


On 26 Nov 2001, Harald Fuchs wrote:

>According to the manual, section "New Features of Full-text Search to
>Appear in MySQL 4.0":
>
>* `*' is a truncation operator.
>
>The query
>  SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versailles')
>returns 2, but
>  SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versaill*')
>returns 0  on MySQL 4.0.
>
>Is this a bug, or do I misunderstand the meaning of "truncation"?
>
>-
>Before posting, please check:
>   http://www.mysql.com/manual.php   (the manual)
>   http://lists.mysql.com/   (the list archive)
>
>To request this thread, e-mail <[EMAIL PROTECTED]>
>To unsubscribe, e-mail <[EMAIL PROTECTED]>
>Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0 in production?

[Sinisa Milivojevic]

johnlucas-Arluna writes:
> Hi folks
> 
> I really need to use some of the new features of version 4, particularly the
> UNION joins.
> 
> Has anyone had any experience with using the UNION, does it work ok and
> fast?
> 
> Also, could you indicate your confidence level with regard to running ver
> 4.0 in production even though it's only beta? I know it's recommended for
> development use now, do we know when it will be declared a stable release?
> 
> We would want to change to 4.0 very quickly, is migrating a ver 3.23.32
> straightforward?
> 
> Many thanks for any help and advice.
> 
> John
> 

Hi!

There are (still) no reported problems with UNION's.

-- 
Regards,
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Fulltime Developer
/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
   <___/   www.mysql.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 updated?

[alec . cawley]

> I think MySQL 4.0.0 is in it's alpha state.

> Wouldn't it be more right to get a 4.0.0 beta and several release
candidates than a 4.0.1 version?

4.0 is in its alpha state. 4.0.0 is the first alpha release, and 4.0.1 the
second and so on. It is, IMO, essential to give every release its own
identifier, so that when a bug is reported you can say "that was fixed in
4.0.2" rather than "that was fixed in last thursdays release". However many
fields you have in your version number, the last must change for every
individual release, be it alpha, beta or full. Release numbers don't cost
money, so we can be prodigal with them if it aids clarity.

 Alec Cawley




-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 updated?

[Bernhard Doebler]

Hi,

I think MySQL 4.0.0 is in it's alpha state.

Wouldn't it be more right to get a 4.0.0 beta and several release candidates than a 
4.0.1 version?

Best regards
Bernhard

- Original Message - 
From: "Mike Wexler" <[EMAIL PROTECTED]>
To: "Mark Maunder" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, November 09, 2001 1:13 AM
Subject: Re: MySQL 4.0 updated?


> When a new version is available it will have a new version number. The 
> current version is 4.0.0 but there will almost certainly be a 4.0.1 
> soon. If you look at the change history in the documentation, there have 
> already been changes put into 4.0.0.
> 


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 updated?

[Mike Wexler]

When a new version is available it will have a new version number. The 
current version is 4.0.0 but there will almost certainly be a 4.0.1 
soon. If you look at the change history in the documentation, there have 
already been changes put into 4.0.0.

If you need quicker access to changes, you can download the source code 
from the bitkeeper tree which changes more frequently.


Mark Maunder wrote:

> Hi,
> 
> Is MySQL 4.0 Alpha updated periodically with bugfixes? i.e. Is it worth
> periodically re-downloading and re-installing MySQL 4.0 to ensure I have
> the most stable version?
> 
> tnx,
> 
> ~Mark.
> 
> 
> -
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> 



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: [MySQL 4.0 compile fails on Linux]

[Sinisa Milivojevic]

Ed Carp writes:
> >Description:
> 
> make[3]: Entering directory `/usr/local/src/mysql-4.0.0-alpha/sql'
> gcc -DMYSQL_SERVER  -DDEFAULT_MYSQL_HOME="\"/usr/local\""  -
> DDATADIR="\"/usr/local/var\""   -DSHAREDIR="\"/usr/local/share/mysql
> \"" -DHAVE_CONFIG_H -I../innobase/include   -I./
> ../include  -I./../regex-I. -I../include -I.
>  -O3 -DDBUG_OFF   -fno-implicit-templates -fno-exceptions -fno-rtti -c sql_lex.c
> c
> sql_lex.cc: In function `void lex_init()':
> sql_lex.cc:85: `symbols' undeclared (first use this function)
> sql_lex.cc:85: (Each undeclared identifier is reported only once
> sql_lex.cc:85: for each function it appears in.)
> sql_lex.cc:85: confused by earlier errors, bailing out
> make[3]: *** [sql_lex.o] Error 1
> 

Hi!

Do:

bk -r edit

The above is defined in lex.h

-- 
Regards,
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, FullTime Developer
/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
   <___/   www.mysql.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: mysql 4.0

[Bill Adams]

Sommai Fongnamthip wrote:

> Hi,
> If I install mysql-4.0 to upgrade in mysql-3.23.xx with old setting value
> (use myisam type), Could I need to change or re-load my old db?

AFAIK, If you are keeping the table type, you can just copy the .MYI, .MYD, and .frm
files to the new location.  Or leave them where they are and point 4.0 to them.

b.



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0 bug with fulltext (case change) updates

[Sergei Golubchik]

Hi!

On Oct 19, Mark Maunder wrote:
> Hi,
> 
> I think this is a bug. The script to recreate the problem is included
> below. This problem appears consistently as long as there's a fulltext
> index and a regular index on the same field and you do an update to
> change the case of a single char.

It is (no, it WAS) a bug.
Fixed, thanks.

> ~mark
> ps: If anyone knows of a workaround please let me know. thanks.

4.0.1 won't have this bug.
If you'd like to fix it yourself - hmm, it's difficult to produce
a patch as fulltext code is changed considerably from 4.0.0, but -
just add a

   error=0;

before
   
   while(old_word->pos && new_word->pos)

in myisam/ft_update.c:174

Regards,
Sergei

-- 
MySQL Development Team
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Osnabrueck, Germany
   <___/

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MYSQL 4.0 bug with fulltext (case change) updates

[Mark Maunder]

Mark Maunder wrote:

> Hi,
>
> I think this is a bug. The script to recreate the problem is included
> below. This problem appears consistently as long as there's a fulltext
> index and a regular index on the same field and you do an update to
> change the case of a single char. It doesn't matter if the fulltext
> index includes other fields. If the regular index is removed, then after
> the insert (where the case of one char in a field is changed) the table
> is briefly marked as crashed, and then seems to automagically fix itself

Just an update to the original post: The table doesn't crash, but the update does
not succeed if the regular index is removed - so this isn't a workaround.


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MySQL 4.0 released

[Richard C. Tucker]

> Britt>  o Lock optimization - MySQL executor acquired
> Britt> more locks than required for common queries.
>
> Just a note: The extra locks are only relevant for Gemini and BDB tables,
> not for MyISAM or InnoDB tables.

The extra locks issue does apply to InnoDB for update statements and select
for update statements.  Of course it does not apply to MyISAM since MyISAM
has neither row level locking or transactions.

-regards
Richard Tuckerhttp://www.nusphere.com
Gemini team member


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MySQL 4.0 released

[Michael Widenius]

Hi!

First I have to apologize to the email list for this discussion: It
certainly doesn't belong here.  On the other hand, as the creator of
MySQL and one who has personally sued by NuSphere corporation I can't
let things like this go unanswered.

> "Britt" == Britt Johnston <[EMAIL PROTECTED]> writes:

Britt> NuSphere is a strong believer in the GPL.  Our history 
Britt> and the 150,000 lines of code we have licensed under the 
Britt> GPL reinforce that fact.

Britt>   http://nusphere.com/releases/062800b.htm  - June 28, 2000
Britt>   http://nusphere.com/releases/013001.htm  - January, 30, 2001

Britt> Please feel free to contact me directly if you would like 
Britt> to discuss this further.

Britt, this is not the right forum to discuss things like this.  You
can't go around the fact that NuSphere violated the MySQL GPL license
by distributing MySQL staticly linked with Gemini without giving the
users access to all the source code.  You also forbid anyone to use
this distribution without having a license from NuSphere.

On your website you even had the following explanation for this:

--
Q: Can I copy NuSphere's products freely and distribute them?
 
A: No, NuSphere's software products are all proprietary,
copyrighted works with licenses that limit distribution. They
cannot be freely copied. The download and CDROM versions of our
products, including NuSphere MySQL and the entire Advantage product
line, cannot be freely copied.

Q: I think all software should be completely free - why isn't
NuSphere's?
 
A: NuSphere believes all software cannot be completely free. We
contribute to Open Source projects that provide free versions of
their software.  Individuals who do not wish to pay to use specific
software are encouraged to join those communities.
--

NuSphere also didn't release Gemini under GPL until MySQL AB sued them
about violating the GPL license and misusing our trademark.  Releasing
Gemini under GPL doesn't however cure the GPL violation, (see
http://www.gnu.org/copyleft/gpl-faq.html).  Until all holders of any
of the violated GPL code has given NuSphere forgiveness, they have
lost all the rights that GPL gives them to the violated code.

Britt, If you want discuss this, you know how to reach me.
I am, as always, ready to discuss ways to solve our differences.

Regards,
Monty

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MySQL 4.0 released

[Michael Widenius]

Hi!

> "Britt" == Britt Johnston <[EMAIL PROTECTED]> writes:

Britt> Now that the patch for Gemini has been created and made 
Britt> available for the new MySQL 4.0 alpha release we are 
Britt> back whole again.

I wouldn't really agree with this.

Britt> I am told that binaries for the complete MySQL 4.0 
Britt> with support for Gemini tables are now available via 
Britt> mysql.org for everyone to use (MyISAM and InnoDB also).
Britt> These MySQL server binaries can be used as-is under the 
Britt> GPL without any requirement for a commercial license
Britt> under any circumstances regardless of the specifics 
Britt> of the application.

NuSphere lawyers have said that the GPL is not enforcable, but we don't
belive that this true.

Because NuSphere has violated the MySQL GPL license, NuSphere has lost
all benefits that the GPL gives, like the right to distribute the
MySQL server.  This means that every download of MySQL from mysql.org
and selling of the boxed products from NuSphere that contains MySQL is
a violation of the rights of MySQL AB.

The GPL also puts restrictions of how a commercial, not open source
product can use the code; Any open source/GPL product can use MySQL
under the GPL license. If your product that uses MySQL is not open
source and you don't want to make it open source, you can't normally
use MySQL under GPL but should get MySQL under an normal commercial
license from MySQL AB.

You can find out more about this at:

http://www.mysql.com/doc/U/s/Using_the_MySQL_server_under_a_commercial_license.html

Britt> As for as 4.0 features you can add the following to 
Britt> the list:

Britt>  o Lock optimization - MySQL executor acquired 
Britt> more locks than required for common queries.

Just a note: The extra locks are only relevant for Gemini and BDB tables,
not for MyISAM or InnoDB tables.



Britt> BTW, MySQL will be a major topic at the Linux Lunacy
Britt> Geek Cruise next week.  NuSphere is the major sponsor 
Britt> for the event helping make it possible for speakers 
Britt> like Richard Stallman, Eric Raymond and Monty along 
Britt> with myself to further the open source revolution.
Britt> Drop me a note if you plan on being there!

Britt, it's ok to email this list that people can meet you on Linux
Lunacy.  However, If you have a commercial message that you believe is
valuable to our users, then please do as everyone else does: Email the
list maintainers and ask for permission to post.

Regards,
Monty

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 released

[Michael Widenius]

Hi!

> "Michael" == Michael Furgal <[EMAIL PROTECTED]> writes:



Michael> Monty and all:

Michael> I have re-applied all the Gemini table handler support and
Michael> ported it to MySQL 4.0.  It is too large to send as an email
Michael> so the patch can be found at:
Michael> ftp://ftp.nusphere.com/MySQL40/mysql40+gemini-patches.tar.gz
Michael> There are 2 files in the patch, once for the configuration files
Michael> and the other for the source code changes.  Both need to be 
Michael> applied.

Michael> The table handler files themselves (ha_gemini.cc and ha_gemini.h)
Michael> have our (NuSphere) copyright on them, however as it has been 
Michael> mentioned many time previously, these files are based on the Berkeley 
Michael> table handler, so we can hold a shared copyright on the handler files.  
Michael> The remaining changes in support of the Gemini component are made to 
Michael> existing files that MySQL AB already holds the copyright to.  
Michael> You are welcome to the copyright of these changes too (even though I 
Michael> believe you already have it, as we have made no claim to it).

Michael> The bottom line is that you are welcome to the copyright on the code
Michael> for all the files/changes in the patch.

Thanks!  As soon as I get this in writing we will re-apply the patch.
Personally I think this email is fine, but our lawyers require us to get
this in writing. This is in line with the recommendations by FSF, who
also require to get things in writing for larger patches like this.
We have actively been communication with the CEO of NuSphere to get
this done, but haven't yet got this.  I hope we will get this in good
time for 4.0.1.

Michael> Please accept this patch so we can move beyond this issue and continue 
Michael> to have a technical relationship.  The business issues between our two
Michael> companies should not prevent the development and maturing of the 
Michael> excellent MySQL Open Source product.

Regards,
Monty

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: MySQL 4.0 - Order By & Limit

[Steve Meyers]

Could you also give a sample of the results you're getting that are incorrect?  You 
don't have to give every field, just the title should do.
 
Steve Meyers


> -Original Message-
> From: Ashwin Kutty [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 18, 2001 11:31 AM
> Cc: [EMAIL PROTECTED]
> Subject: RE: MySQL 4.0 - Order By & Limit
> 
> 
> 
> Point well taken.. The query is as follows:-
> 
> SELECT * FROM dddeli WHERE title LIKE "%$keyword%" ORDER BY title 
> desc LIMIT $start,$end;
> 
> Where $keyword is the keyword to search by from the field title, $start
> and $end are to dictate which page of the results, etc..
> 
> title is varchar(128)
> 
> and dddeli has 33 fields..
> 
> On Thu, 18 Oct 2001, Steve Meyers wrote:
> 
> > It would help if you posted the actual query and results you 
> are getting, instead of showing "simulated" results.  You mention 
> the query below in your first post, but you never give the actual 
> results of it.
> >  
> > Steve Meyers
> > 
> > 
> > > -Original Message-----
> > > From: Ashwin Kutty [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, October 18, 2001 5:58 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: MySQL 4.0 - Order By & Limit
> > > 
> > > 
> > > 
> > > I just saw the mistake I made in my original post.. I want to Order By
> > > letter, but when I do that with the Limit clause the results are as
> > > shown in the original post.. Anyone know what the problem could be?
> > > 
> > > 
> > > Steve Meyers wrote:
> > > 
> > > >That is actually how it is supposed to work -- MySQL gets all 
> > > the rows, sorts them, and then returns up to the limit.  What you 
> > > suggest would make no sense in any application, as far as I can 
> > > tell.  The problem with the SQL queries given in the original 
> > > post is the the ordering is being done by #, not letter.  Of 
> > > course it will be fairly haphazard.  If you want to sort by 
> > > number, then letter, you will need to specify it in your query as 
> > > such (ORDER BY #, letter).
> > > > 
> > > >Steve Meyers
> > > >
> > > >
> > > >>-Original Message-
> > > >>From: Fournier Jocelyn [Presence-PC] [mailto:[EMAIL PROTECTED]]
> > > >>Sent: Tuesday, October 16, 2001 1:31 PM
> > > >>To: [EMAIL PROTECTED]
> > > >>Cc: [EMAIL PROTECTED]
> > > >>Subject: Re: MySQL 4.0 - Order By & Limit
> > > >>
> > > >>
> > > >>Hi,
> > > >>
> > > >>I don't see the interest of this kind of behaviour : the 
> main benefit of
> > > >>LIMIT is MySQL stops fetching rows as soon as the number of 
> > > rows specified
> > > >>in LIMIT is achieved.
> > > >>The behaviour you describe requires that MySQL fetches all the 
> > > rows, sorts
> > > >>it, and then applies LIMIT. (so no speed optimization !).
> > > >>For your example, just use the SQL query without LIMIT, and 
> > > then get only
> > > >>the rows that interest you :) (I assume you are using 
> language like PHP,
> > > >>C++, etc... to execute this query ?)
> > > >>
> > > >>Regards,
> > > >>
> > > >>Jocelyn Fournier
> > > >>Presence-PC
> > > >>
> > > >>- Original Message -
> > > >>From: "Ashwin Kutty" <[EMAIL PROTECTED]>
> > > >>Cc: <[EMAIL PROTECTED]>
> > > >>Sent: Tuesday, October 16, 2001 8:48 PM
> > > >>Subject: MySQL 4.0 - Order By & Limit
> > > >>
> > > >>
> > > >>>Hi,
> > > >>>
> > > >>>I thought version 4.0 was supposed to do a Order By first 
> and then a
> > > >>>Limit after that on the results returned on a SELECT.. I have just
> > > >>>installed the new version and I hit the same problem I was hitting
> > > >>>before, i.e., the Limit seems to be executing first and 
> then the Order
> > > >>>By causing all the results to be haphazard when they 
> display.. Now if I
> > > >>>go for a wider set of results, i.e. increase the Limit, the 
> > > results come
> > > >>>a lot better then, i.e. more of them are ordered right, but 
> > > then, 

RE: MySQL 4.0 released

[Britt Johnston]

Now that the patch for Gemini has been created and made 
available for the new MySQL 4.0 alpha release we are 
back whole again.

I am told that binaries for the complete MySQL 4.0 
with support for Gemini tables are now available via 
mysql.org for everyone to use (MyISAM and InnoDB also).
These MySQL server binaries can be used as-is under the 
GPL without any requirement for a commercial license
under any circumstances regardless of the specifics 
of the application.

As for as 4.0 features you can add the following to 
the list:

o SHOW LOCKS statement

o Gemini performance improvements in checkpoint
processing and cluster reuse (recovery log).

o Lock optimization - MySQL executor acquired 
more locks than required for common queries.

o General bug fixes to core MySQL function
that benefit Gemini.

We have done recent benchmarks with IBM and OSDL on MySQL
with Gemini which we presented preliminary results at Open 
Source Database summit conference a few weeks ago.  If 
anyone is interested in those slides please let me know.

BTW, MySQL will be a major topic at the Linux Lunacy
Geek Cruise next week.  NuSphere is the major sponsor 
for the event helping make it possible for speakers 
like Richard Stallman, Eric Raymond and Monty along 
with myself to further the open source revolution.
Drop me a note if you plan on being there!

Britt...

-- 
*** NuSphere Advantage *** Winner Best Developer Tool ***
  LinuxWorld 2001

D. Britton Johnston   603-578-6707 Nashua
Chief Technology Officer  781-280-4954 Bedford
NuSphere Corporation  781-280-4600 Main
14 Oak Park   781-280-4646 Fax
Bedford, MA 01730 www.nusphere.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: MySQL 4.0 released

[Michael Furgal]

> Hi!
> 
> > "Michael" == Michael T Babcock <[EMAIL PROTECTED]> writes:
> 
> Michael> On Wed, Oct 17, 2001 at 12:49:26AM +0300, Michael Widenius wrote:
> >> We agreed a long time ago with NuSphere that the small hooks would be
> >> copyrighted by MySQL AB, but as the concrete paperwork has not been
> >> signed, we felt we had to remove them.
> 
> Michael> For the sake of those who wish to use Gemini tables, would you
> Michael> consider offering the patch, as 'pushed into bitkeeper' on the
> Michael> downloads page seperately?
> 
> The problem with this is that it would be very hard for us to keep
> this up to date 'outside of MySQL' as we are just now doing some major
> redesign of how tables are used inside MySQL; We are doing this to get
> MySQL to reuse memory better, get more speed and remove a 'not that
> nice' block around 'open table'.
> 
> We have however to consider this, if we can't get the copyright
> assignment from NuSphere in the near future.
> 
> Michael> Michael T. Babcock
> Michael> CTO, FibreSpeed Ltd.
> 
> Regards,
> Monty

Monty and all:

I have re-applied all the Gemini table handler support and
ported it to MySQL 4.0.  It is too large to send as an email
so the patch can be found at:
ftp://ftp.nusphere.com/MySQL40/mysql40+gemini-patches.tar.gz
There are 2 files in the patch, once for the configuration files
and the other for the source code changes.  Both need to be 
applied.

The table handler files themselves (ha_gemini.cc and ha_gemini.h)
have our (NuSphere) copyright on them, however as it has been 
mentioned many time previously, these files are based on the Berkeley 
table handler, so we can hold a shared copyright on the handler files.  
The remaining changes in support of the Gemini component are made to 
existing files that MySQL AB already holds the copyright to.  
You are welcome to the copyright of these changes too (even though I 
believe you already have it, as we have made no claim to it).

The bottom line is that you are welcome to the copyright on the code
for all the files/changes in the patch.

Please accept this patch so we can move beyond this issue and continue 
to have a technical relationship.  The business issues between our two
companies should not prevent the development and maturing of the 
excellent MySQL Open Source product.

Thank You.

MikeF
-- 
Mike Furgal 
Manager - Gemini Technology
http://www.nusphere.com

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php