Re: revoke SELECT on a column [ MySQL 4.1 ]

Hi, No... You have applied TABLE level GRANT PRIVILEGES and tried to REVOKE that with COLUMN PRIVILEGES. Hence the error. To Fix it, apply column privileges --- mysql GRANT SELECT(hide_this) ON the_base.t100 to 'a_user'@'localhost' identified by 'a_passwd'; mysql select * from

Re: Updating from 4.0.20 to 5.0.27

On 2007-02-06 Dan Nelson wrote: In the last episode (Feb 06), Tim Johnson said: I'm currently using OS linux slackware 10.0 with MySQL version 4.0.20 I currently use python and rebol APIs to MySQL, not PHP. I've downloaded mysql-standard-5.0.27-linux-i686.tar.gz Questions: Should

Re: mysql limits

Search speeds and CPU with MyISAM is quite good. I tried InnoDb and insert speeds was far too slow because of its row locking versus MyISAM's table locking. Some people have been able to fine tune InnoDb but it requires even more RAM because InnoDb works best when the entire table fits into

Re: revoke SELECT on a column [ MySQL 4.1 ] + column privileges

hello, first thanks to ViSolve DB Team, and since then, my question turns out to be : in the base that contains a table of 100 columns, I want to disable SELECT on only 1 column hide_this, how to apply column privileges using a loop in mysql, that could do : for each column in the_base.t100

A 'Simple' Protocol for Manual MySQL Slave Promotion to Master

Hey. I should have posted this hear earlier but it just dawned on me that you guys could have some good feedback: We've been working on the design of a protocol which would enable promotion of a slave to a master in a MySQL replication cluster. Right now, if a MySQL master fails, most people

Re: A 'Simple' Protocol for Manual MySQL Slave Promotion to Master

HB, MON, IPFail would work well for this , here is some info from my website that I wrote very long ago, hope it helps http://kjalleda.googlepages.com/mysqlfailover http://kjalleda.googlepages.com/automatedmasterfailoverinmysql Kishore Jalleda On 2/7/07, Kevin Burton [EMAIL PROTECTED] wrote:

implementation of SELECT ... ORDER BY RAND() LIMIT 1

Hi all, I have a question about the combination of RAND and LIMIT 1. If I have a query like: SELECT ... ORDER BY RAND() LIMIT 1 with the ... replaced with a normal query on one table. How is this implemented? Is this optimized for the fact that it only needs one entry? And what about when

Re: implementation of SELECT ... ORDER BY RAND() LIMIT 1

I have a question about the combination of RAND and LIMIT 1. If I have a query like: SELECT ... ORDER BY RAND() LIMIT 1 with the ... replaced with a normal query on one table. How is this implemented? Is this optimized for the fact that it only needs one entry? Try prefixing your query with

about partition key type

mysql create table t1 (num int(10) not null, id char(18) not null) partition by range(id) ( partition id1 values less than('12'), partition id2 values less than('23'), partition id3 values less than('34'), partition id4 values less

improve performance for query statements with LIKE keyword

Hi all, Is there some way to improve performance for query statments with LIKE keyword ? like this: mysql select id,name,title,description from books where description like '%some_strings%'; Note: Above some_strings is CJK(Chinese or Japanese or Korean). I know MySQL cann't support CJK

Re: about partition key type

In the last episode (Feb 08), xian liu said: mysql create table t1 (num int(10) not null, id char(18) not null) partition by range(id) ( partition id1 values less than('12'), partition id2 values less than('23'), partition id3 values less