hi,
AFAIK, if we start mysqld with --low-priority-updates, it sets table updation a
lower priority than the SELECT statements, irrespective of storage engines.
hence it will affect the priority of the update operation.
Ref: http://mysql.justdn.org/doc/refman/5.1/en/table-locking.html
-
Not sure if this is possible or not. But I've two identical tables in two
different databases. Is it possible to retrieve data from the different
tables in one query ?
Thanks
Neil
_
MSN Hotmail is evolving check out the new
Not sure if this is possible or not. But I've two identical tables in two
different databases. Is it possible to retrieve data from the different
tables in one query ?
Yes, by using this notation:
select *
from mydatabase.mytable
Martijn Tonies
Database Workbench - development tool for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Tompkins schrieb:
Not sure if this is possible or not. But I've two identical tables in
two different databases. Is it possible to retrieve data from the
different tables in one query ?
(SELECT * FROM db1.table) UNION (SELECT * FROM
The databases are on the same server, however the login details for each
database are different.
From: Martijn Tonies [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Re: Query Two Databases
Date: Thu, 25 Jan 2007 11:56:37 +0100
Not sure if this is possible or not. But I've two
On Thursday 25 January 2007 11:08, Neil Tompkins wrote:
The databases are on the same server, however the login details for each
database are different.
A query executes with the credentials of the authentication used to set up the
connection. If you want to query two tables simultaneously
The databases are on the same server, however the login details for each
database are different.
Hmm, I guess that the currently connected user needs to have access
to both databases, how else would it get the data?
Martijn Tonies
Database Workbench - development tool for MySQL, and more!
Hi,
try
CREATE INDEX geo_idx ON users(entity_id, user_type);
Filip
Alex Arul napsal(a):
and also an index on users.entity_id (will help the join) should solve your
problem.
Thanks
Alex
On 1/24/07, Brent Baisley [EMAIL PROTECTED] wrote:
You should create indexes on the fields you search
Thanks!
OK, here's where my understanding of MySQL and how indices work get
fuzzy.
In my scenario what would the difference between (I tested with
different indices these and included the query times with the EXPLAIN
outputs):
(1) creating separate indices on entity_id and also on
I am doing tests so I want to easy take my DB and make a full copy of
it into a test db everytime I want to test something against the
non-produciton version of DB. What is the easiest way to do this.
So I have a DB called backlog and I want to copy it's structure and
data into backlog_test
I am doing tests so I want to easy take my DB and make a full copy of
it into a test db everytime I want to test something against the
non-produciton version of DB. What is the easiest way to do this.
So I have a DB called backlog and I want to copy it's structure and
data into backlog_test
all,
I have been tasked with upgrading a critical 3.23.55 database to 5.0(.27-ish).
short version is it's never been upgraded because authors have moved on and
nobody's sure of everything that uses it.
I enabled the general log a few days ago and have a good body of data with
which to go code
Hi All
I know the innodb vs myisam issue comes up quite frequently. I went through
old threads and could not find an answer to my questions.
Generally, is there any reason/scenario not to use innodb?
From a feature perspective, I do not need full text indices, foreign keys
are usefull but not
On 1/25/07, Sid Lane [EMAIL PROTECTED] wrote:
all,
I have been tasked with upgrading a critical 3.23.55 database to 5.0
(.27-ish).
short version is it's never been upgraded because authors have moved on
and
nobody's sure of everything that uses it.
I enabled the general log a few days ago and
Size is an issue with InnoDB and deleting records does not reduce the size of the file. In my experience, the performance drop off
is considerable once the table reaches a certain size. And it's not a slight drop off over time.
If your table is going to get very large, I would reccommend using
On Friday 26 January 2007 06:17, Olaf Stein wrote:
From a feature perspective, I do not need full text indices,
This is about the only reason I've seen MyISAM promoted as table engine of
choice.
I know this is a very general question but it seems not to make any sense
not to use innodb
Another thing to consider is:
heh, silly mail client :). Another thing to consider is this:
http://dev.mysql.com/doc/falcon/en/index.html
Though it's Not recommended for production use, I've heard people still use
it in production environments.
--
Chris White
PHP Programmer
Interfuel
--
Hi Olaf,
I know the innodb vs myisam issue comes up quite frequently. I went
through
old threads and could not find an answer to my questions.
Generally, is there any reason/scenario not to use innodb?
From a feature perspective, I do not need full text indices, foreign keys
are usefull
At 03:54 PM 1/25/2007, you wrote:
Another thing to consider is:
heh, silly mail client :). Another thing to consider is this:
http://dev.mysql.com/doc/falcon/en/index.html
Though it's Not recommended for production use, I've heard people still use
it in production environments.
--
Chris,
We have 5.0.27 installed on a CentOS machine that doesn't have a ton
of disk space. Is it possible to point the data directory to lie on a
samba connected share? The samba share does not support Unix file
permissions so it is not possible to set mysql as the owner of the
files. Is this
Hi,
i have a system that has media files == users can be fans of media ( so
media becomes their favorite ).
the table itself:
CREATE TABLE media_fans(
id int(11) unsigned not null auto_increment,
user_id int(11) unsigned not null,
media_id int(11) unsigned not null,
primary key(id),
21 matches
Mail list logo
