Håkon Eriksen wrote:
Is there a way of turning on the general query log in the my.cnf file
or do I have to edit the init-script?
Yes, all command-line options can be specified in my.cnf. Read the
following page for more info:
http://www.mysql.com/doc/O/p/Option_files.html
-myk
Justin,
The error message states that you have a syntax error in the CREATE
DATABASE statement. This is probably just a typo, but the only way for
us to diagnose the problem is for you to post the exact statement that
gives you the error.
-myk
justin cunningham wrote:
mysqladmin: CREATE
saraswathy saras wrote:
is there any other specific command instead order by ID DESC to select
all the record from table where the ID is the last ID.The ID is
autoincrement.
Not sure from your message if you already know this, but ORDER BY ID
DESC LIMIT 1 gives you what you want.
-myk
Amy Zediak wrote:
I'm trying to install Bugzilla and according to the instructions you
have to make a few changes to MySQL and i'm a little confused. It says
that you have to add mysqld to init script and then add -0
max_allowed_packet=1M to the command that starts mysqld. I'm not
completely
Chris Knipe wrote:
I'm currently storing them into varchar(16), although I've been thinking of
doing it as for smallint columns, but then I can't be 100% certain I won't
get duplicates.
Why not? Just define a UNIQUE index across all four smallint columns,
and MySQL will throw an error if
abw wrote:
Is it possible to zip up database directories on one server and move
them to another server, then simply unzip them?
Yes.
If so, once that is done, does something need to be done to mysql so
it is aware of the databases? Is there some file that has a list of
databases that
Chris Knipe wrote:
Multiple subnets :/
columns like this:
octet1, octet2, octet3, octet4
195,196,192,23
232,196,231,11
This would then be seen as a duplicate
Not if you have a single index spanning all four columns (as opposed to
four indexes, one on each column). With the single
Stavros Patiniotis wrote:
Hello,
My hard drive has just failed on my database server, and I have rebuilt it
and copied the data from backups back on to the drive, however mySQL
cannot see all of the databases.
A 'show databases' shows all of the databases, however 'use DBNAME' says
ERROR
Michael Widenius wrote:
You can check if the index are ok with CHECK TABLE; If this says the
index is ok, they are not corrupted.
Apparently this doesn't work in all cases. CHECK TABLE told me
everything was fine, but dumping the data to a dump file via mysqldump
and then re-importing it
Devon Harding - GTHLA wrote:
Where can I find some info on mysql performance tuning?
http://www.mysql.com/doc/M/y/MySQL_Optimisation.html
-myk
-
Before posting, please check:
http://www.mysql.com/manual.php (the
How do I optimize the following query?
SELECT foo.id FROM foo, bar WHERE foo.id = bar.foo_id AND foo.field =
'baz' OR bar.field = 'baz';
Only a small number of records from each table match the query
conditions, but MySQL takes forever to execute it. No wonder, when
EXPLAIN says it needs to
[EMAIL PROTECTED] wrote:
The form Select foo.id From foo, bar... is giving you a cross-product. A
cross-product emits a row for every combination of rows from each of your
tables. The Explain results seem to be consistent with this. What I'd
suggest is that you try a Join on your tables.
Thanks
Steven Roussey wrote:
Are the tables defined the same on both servers?
Yes, the tables are defined exactly the same.
Is the data the same?
Just about. The data on the working server is a copy of the database on
the broken server. For previous tests I used a several-weeks-old copy
of the
I haven't found the problem, but I seem to have found the solution. If
I dump the data and re-import it (causing the index files to be
re-created from scratch), the indexes work fine. I think this problem
started when I upgraded from MySQL 3.22.30 to 3.23.44 and converted the
tables from
Steven Roussey wrote:
The corollary to the above quote is that MySQL can not use indexes with
an OR clause at the base level.
MySQL *does* use the index on a different server, though, it just
doesn't use the index on that server. Compare the results of EXPLAIN
queries on the two servers
MySQL 3.23.44 isn't using indexes when it should and could, even when I
try to force it via a USE INDEX clause in the SELECT statement. For
example, here is what EXPLAIN gives me on a query containing the clause
USE INDEX (bug_status) on the bugs table:
mysql EXPLAIN SELECT DISTINCT
I have some more information about the problem. It seems to be caused
by the presence of an OR or IN clause in the WHERE portion of the query.
Without the clause, 2.23.44 uses the appropriate indexes, but with the
clause it does not. 2.23.41 uses the appropriate indexes in both cases.
I can't figure out how to formulate a query to retrieve a certain set of
data. I have two tables in a many-to-many relationship with each other
via a linking table. I want to get a list of the records in the first
table which have no matching records of a certain value in the second
table
Jeremy Zawodny wrote:
On Fri, Jan 18, 2002 at 03:12:22PM +0100, Myk Melez wrote:
Is it possible to replicate between two databases on a single
server, and if not, then what is the next best solution?
It is possible, yes.
Is there any way to do it with a single instance of MySQL (replicating
Is it possible to replicate between two databases on a single server,
and if not, then what is the next best solution? I administer a
Bugzilla installation with about 1.8GB in a MySQL database. Bugzilla
has a built-in replication solution that copies data from a primary
database optimized
20 matches
Mail list logo
