Cliff,
- Original Message -
From: ""Cliff"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Saturday, March 13, 2004 11:32 PM
Subject: Re: InnoDB tables using 90% cpu
> Well I recompiled with Linuxthreads with the same result. I ran explain o
Chris Nolan" <[EMAIL PROTECTED]>
To: "Sasha Pachev" <[EMAIL PROTECTED]>
Cc: "Cliff" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, March 09, 2004 7:14 PM
Subject: Re: InnoDB tables using 90% cpu
> Sasha Pachev wrote:
>
> > Cliff
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 09, 2004 4:56 PM
Subject: Re: InnoDB tables using 90% cpu
> The query is running dramatically slower than the MyISAM query,
sometimes
> even causing mysql to freeze for a while. I searched this list and
found a
> few people saying that
Sasha Pachev wrote:
Cliff wrote:
The query is running dramatically slower than the MyISAM query,
sometimes
even causing mysql to freeze for a while. I searched this list and
found a
few people saying that on FreeBSD mysql should be compiled using linux
pthreads if you are using InnoDB or else I
Cliff wrote:
The query is running dramatically slower than the MyISAM query, sometimes
even causing mysql to freeze for a while. I searched this list and found a
few people saying that on FreeBSD mysql should be compiled using linux
pthreads if you are using InnoDB or else I would get this exact pr
this been resolved or is should I recompile? I am using native freebsd
threads.
- Original Message -
From: "Sasha Pachev" <[EMAIL PROTECTED]>
To: "Cliff" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, March 08, 2004 9:18 AM
Subject: Re:
Cliff wrote:
Hi, I have a whole database I wanted to convert to InnoDB from MyISAM, but
do not want to use alter table because of the problems I had last time. I
made a whole dump of the table using mysqldump and changed all of the table
create definitions from MyISAM to InnoDB. Theoretically this
Irwin,
DROP FOREIGN KEY was implemented after 4.1.0.
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for MySQL
Order MySQL technical support from https://order.mysql.com/
- Origi
At 10:35 -0500 12/19/02, Deepa wrote:
While creating InnoDB tables, I was not able to specify a "fulltext "
column in the table creation sql. Is this a bug or a limitation with InnoDB
? There could be quite a few users who need FULLTEXT feature with InnoDB.
It's like the manual says: FULLTEXT i
On Thu, 19 Dec 2002, Deepa wrote:
> While creating InnoDB tables, I was not able to specify a "fulltext "
> column in the table creation sql. Is this a bug or a limitation with InnoDB
> ? There could be quite a few users who need FULLTEXT feature with InnoDB.
It's a feature :-(
FULLTEXT has not y
At 12:44 +0200 10/25/02, Natale Babbo wrote:
i tried it ... but nothing to do!
when mysql parse the foreign key in the create table i
get the error.
perhaps i'm wronging in restoring tables/db!
i use this method:
shell> mysql -u -p <
is it wrong?
Depends.
- DId you add the SET FOREIGN_KEY_
Natale,
Friday, October 25, 2002, 1:44:19 PM, you wrote:
NB> i tried it ... but nothing to do!
NB> when mysql parse the foreign key in the create table i
NB> get the error.
NB> perhaps i'm wronging in restoring tables/db!
NB> i use this method:
shell> mysql -u -p <
NB> is it wrong?
What vers
i tried it ... but nothing to do!
when mysql parse the foreign key in the create table i
get the error.
perhaps i'm wronging in restoring tables/db!
i use this method:
shell> mysql -u -p <
is it wrong?
thanks.
Natale Babbo
--- Victoria Reznichenko
<[EMAIL PROTECTED]> ha scritto: >
Natale,
Natale,
Friday, October 25, 2002, 10:08:00 AM, you wrote:
NB> ok ... that's right for data (insert into ...) ... but
NB> i get the error before ... when mysql try to create
NB> child table:
NB> CREATE TABLE ... idParent BIGINT, INDEX idpar_ind
NB> (idParent), FOREIGN KEY (idParent) REFERENCES
NB>
ok ... that's right for data (insert into ...) ... but
i get the error before ... when mysql try to create
child table:
CREATE TABLE ... idParent BIGINT, INDEX idpar_ind
(idParent), FOREIGN KEY (idParent) REFERENCES
parent(id)
.. when mysql parses the foreign key, parent table
doesn't exist yet!
b
... can someone add InnoDB to the list of keywords?? SQL ... QUERY ...
Victoria Reznichenko wrote:
You can set up SET FOREIGN_KEY_CHECKS=0, in this case foreign key
constraints will not be checked. It's supported since 3.23.52 and
4.0.3
Out of curiousity, are the foreign key constraints check
Natale,
Thursday, October 24, 2002, 10:57:00 AM, you wrote:
NB> Anyone knows how to backup innodb tables in the right
NB> sql order?
NB> ... i mean ... to allow restoring correctly
NB> without foreign key constraint violation (if in the
NB> backup file ddl code for the child table is before ddl
NB
nf options as recommended in section
2 of http://www.innodb.com/ibman.html.
Regards,
Heikki
- Original Message -
From: "Oren Zeev-Ben-Mordehai" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Sent: Tuesday, May 07, 2002 5:26 PM
Sub
Oren,
what MySQL version you are running? What OS?
Send me a copy of your my.cnf, the error log 'hostname'.err, and the exact
sequence of SQL statements you used to crash InnoDB, including the table
CREATE statements. Did InnoDB run out of tablespace?
Regarding the performance, did you set inn
On Tue, Apr 09, 2002 at 10:17:56AM +0200, Luke van Blerk wrote:
> Hi everyone,
>
> I've been reading up about InnoDB tables and they seem to have lots
> of advantages. I'm particularly interested in using the foreign keys
> as this will save me some much need time. In the benchmark tests on
> the
nk about
it, let alone code it.
-JF
> -Original Message-
> From: Richard Clarke [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 09, 2002 5:11 AM
> To: [EMAIL PROTECTED]
> Subject: Re: InnoDB tables
>
>
> Luke,
>
> How exactly will the foreign keys save y
ys. What do you think?
Regards
Luke
- Original Message -
From: "Richard Clarke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 2:11 PM
Subject: Re: InnoDB tables
> Luke,
>
> How exactly will the foreign keys save you time? Please ex
Luke,
How exactly will the foreign keys save you time? Please explain.
Ric.
- Original Message -
From: "Luke van Blerk" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 9:17 AM
Subject: InnoDB tables
> Hi everyone,
>
> I've been reading up about InnoDB tab
Hi,
does any1 know what is the earliest version of Mysql
for Solaris, with support for InnoDB?
If I am not mistaken, the version that we have is
3.23.32.
Can MySql Max be added or some patch be added?
This is not on a personal machine. It's on a server
in my department (computer's science) and
Hi!
-Original Message-
From: "j.random.programmer" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Date: Saturday, March 02, 2002 5:21 AM
Subject: Re: Innodb tables lose foreign keys after creating an index...
>
>--- Heikki Tuuri <[EMAIL PROTECTED]> w
--- Heikki Tuuri <[EMAIL PROTECTED]> wrote:
> Rick,
>
> sorry, it is not mentioned in the manual that MySQL
> performs a CREATE INDEX
> by doing an ALTER TABLE. And ALTER TABLE has the
> feature (= documented bug)
> that it removes foreign key definitions.
Heikki:
Is there a fix planned for th
Rick,
sorry, it is not mentioned in the manual that MySQL performs a CREATE INDEX
by doing an ALTER TABLE. And ALTER TABLE has the feature (= documented bug)
that it removes foreign key definitions.
You should define all your indexes within the table create statement, like
in:
CREATE TABLE pare
On Fri, 2001-10-05 at 23:59, Benjamin Pflugmann wrote:
> Hi.
>
> Heikki, please correct me, if I say something stupid. ;-)
>
> On Fri, Oct 05, 2001 at 10:07:04AM -0700, [EMAIL PROTECTED] wrote:
> > Deryck, others:
> >
> > I'm doing some reading on InnoDB and am pretty ignorant on the subjets.
>
Hi.
Heikki, please correct me, if I say something stupid. ;-)
On Fri, Oct 05, 2001 at 10:07:04AM -0700, [EMAIL PROTECTED] wrote:
> Deryck, others:
>
> I'm doing some reading on InnoDB and am pretty ignorant on the subjets.
> Can someone explain why would InnoDB be faster than MySQL?
Please not
Deryck, others:
I'm doing some reading on InnoDB and am pretty ignorant on the subjets.
Can someone explain why would InnoDB be faster than MySQL? From what I read
it looks like it will have more overhead to support the transactions
and that should decrease the performance rather than improve it.
Thanks you for the URL. (:>
I just added to my collections.
Daniel
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ilya
> Martynov
> Sent: Friday, October 05, 2001 04:06
> To: Daniel Ouellet
> Cc: Deryck Henson; MySQL
> Su
On Mon, 2010-10-04 at 19:32, Deryck Henson wrote:
> The original query is as follows:
>
> SELECT * FROM websites WHERE category LIKE '%"&search&"%' OR keywords LIKE
> '%"&search&"%' OR description LIKE '%"&search&"%'
>
> The "&search&" instances are from an ASP page. 'search' is a variable that
DO> Here is two thing for you.
DO> First, GREAT source for search of pass problem on any thing really.
DO> http://marc.theaimsgroup.com/
DO> Then, information on the InnoDB. Not hard to find really.
DO> http://www.mysql.com/documentation/mysql/bychapter/manual_Table_types.html#I
DO> nnoDB
I w
Deryck,
the latest information on InnoDB you can always find at
http://www.innodb.com
Regards,
Heikki
Innobase Oy
>Here is two thing for you.
>
>First, GREAT source for search of pass problem on any thing really.
>
>http://marc.theaimsgroup.com/
>
>Then, information on the InnoDB. Not hard to
I love this one! (:>
That put a smile on a long night!
Thanks!
Daniel
> The original query is as follows:
>
> SELECT * FROM websites WHERE category LIKE '%"&search&"%' OR keywords LIKE
> '%"&search&"%' OR description LIKE '%"&search&"%'
>
> The "&search&" instances are from an ASP page. 'sea
Here is two thing for you.
First, GREAT source for search of pass problem on any thing really.
http://marc.theaimsgroup.com/
Then, information on the InnoDB. Not hard to find really.
http://www.mysql.com/documentation/mysql/bychapter/manual_Table_types.html#I
nnoDB
Have a good reading.
Danie
The original query is as follows:
SELECT * FROM websites WHERE category LIKE '%"&search&"%' OR keywords LIKE
'%"&search&"%' OR description LIKE '%"&search&"%'
The "&search&" instances are from an ASP page. 'search' is a variable that
is asigned the value of the query string 'search'
dim search
Alex,
slowness of count(*) is a well-known problem.
I will fix it some time this fall. Not very easy,
because of multiversioning and recovery.
The other problem you have is that a delete operation
ends up in a deadlock (I think it should not be called
a 'crash').
I will write in October a selec
38 matches
Mail list logo
