On Wed, Jun 13, 2007 at 12:50:03PM -0700, Mufaddal Khumri wrote:
mysql select * from t1 where sid != 2;
As you can see, the rows that had sid = NULL did not get returned in
the results when i did ... where sid != ;
Question: Is this behaviour correct and is in accordance to the SQL
On Tue, Jun 12, 2007 at 11:09:41AM -0400, kalin mintchev wrote:
I guess a lot of that depends what an acceptable query execution time for
you is.
well... i don't really know. 30 secs maximum?! i've never worked with
such huge tables. 3 - 5 million records is fine but i've never worked on
On Fri, Jun 08, 2007 at 03:14:18PM +0530, Ananda Kumar wrote:
How do i give only select privilege to a specific database.
GRANT SELECT ON abc.* to 'ab'@'%' identified by 'ab';
Like that.
mysql select select_priv from user where user='qa';
+-+
| select_priv |
+-+
On Fri, Jun 08, 2007 at 04:25:00PM +0530, Ananda Kumar wrote:
So, what ever i did is right?
Yes. User 'ab' can SELECT on all tables in database 'abc'.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
On Wed, Jun 06, 2007 at 05:56:44PM -0700, Peter Rosenthal wrote:
On 04/06/07, Jon Ribbens [EMAIL PROTECTED] wrote:
Um, what? Both that and the methods described in the magazine are
completely wrong. You use mysql_real_ecape_string(), that's it.
I would disagree on the use
On Mon, Jun 04, 2007 at 02:44:25PM -0700, Daevid Vincent wrote:
Thanks for the magazine. I already incorporated a little extra SQL
injection checking into my db.inc.php wrapper...
//[dv] added to remove all comments (which may help with SQL injections
as well.
$sql =
On Tue, May 15, 2007 at 04:13:33PM -0500, Kenneth Loafman wrote:
Can't tell. The docs are somewhat lacking in detail, however, if I do a
db.autocommit(True) it works as it should.
Will have to dig into the API code and see if that is where the semantic
discontinuity lies.
The
On Tue, May 15, 2007 at 06:39:21PM -0500, Kenneth Loafman wrote:
Interesting... guess the intent was a disconnect that would break code
trying to work on MySQL, regardless of engine selected. That decision
makes it two products, MySQL/MyISAM and MySQL/InnoDB with different
semantics. Yes,
On Thu, May 10, 2007 at 05:17:12PM +0100, Jon Ribbens wrote:
I suspect some sort of bug in the MySQLd authentication code.
I've managed to discover using --debug that it's due to MySQLd failing
to handle EINTR from read() in the authentication stage.
I've filed a bug report: http
On Thu, May 10, 2007 at 03:37:26AM +0100, Jon Ribbens wrote:
I've just upgraded all the clients and servers to 5.0.41 (which looks
like it just came out); I'll see what happens.
It hasn't solved the problem, but it has changed the error message to:
OperationalError:
(2013, Lost
On Thu, May 10, 2007 at 08:58:37AM -0600, mos wrote:
If you do a google search:
http://www.google.ca/search?q=lost+mysql+connection+%22reading+authorization+packet%22hl=enstart=90sa=N
you'll find about a hundred web sites encountering the exact same error.
Indeed, I noticed that ;-)
Maybe
We are using MySQL 5.0.27 on RedHat Enterprise Linux ES release 4,
and the MySQL-python-1.2.1_p2 connector.
We are getting intermittent mysterious errors as follows:
OperationalError:
(2013, 'Lost connection to MySQL server during query')
when attempting to connect to the MySQL server
On Wed, May 09, 2007 at 09:22:34AM -0400, Michael Dykman wrote:
I realize that's quite unlikely that you have performed a similar
sloppy import but there is likely some edge condition on your server
(wierd permissions in the data directory, corruoted tables, etc.)
but I still recommend that
On Wed, May 09, 2007 at 11:17:59AM -0400, Michael Dykman wrote:
When we first examined our server logs, we saw the same.. in our case
(again) it was only when we slowed down and examined the timestamps on
the start/stop messages that we realized that the server was
restarting at unexpected
On Wed, May 09, 2007 at 07:14:38PM +0200, Martijn Tonies wrote:
I have a table of properties that is linked to a table f images with a one
property to many images relationship. I have manged this with nested
queries but want to try and do it on one line. My current query
$query = SELECT *
On Wed, May 09, 2007 at 10:07:41PM -0400, Mathieu Bruneau wrote:
We found a similar issue because we were using persistent connection in
php and had a firewall between the mysql and the webserver. The problem
is that our persistent connection were setup for lasting up to something
like 8 hours
Miles Thompson [EMAIL PROTECTED] wrote:
At 07:56 AM 11/1/2006, Leandro Guimarães Faria Corcete DUTRA wrote:
snip .. further notices; and SolidDB, which
is still β.
Help this poor English-speaker - what's the symbol you use to describe
SolidDB?
I assume it is a beta character, since
I have a simple single-table SELECT query that takes of several
minutes to complete, due to a very large number of result rows being
involed. I don't think there is any way to optimise the query - MySQL
is already using the appropriate index etc, it's just a huge table and
the query has a large
Does nobody have any ideas on this? It's quite perplexing.
It's MySQL Ver 14.6 Distrib 4.1.5-gamma, if it makes a difference.
Jon Ribbens [EMAIL PROTECTED] wrote:
I am getting Error 136 No more room in index file on a table,
but the table does not appear to be full in any way. As you can see
I am getting Error 136 No more room in index file on a table,
but the table does not appear to be full in any way. As you can see
from the myisamchk -dv output below, both the datafile length and
the keyfile length are much smaller than their respective maximums.
The table is on a Linux ext3
20 matches
Mail list logo
