v + 659
>
>
> Is this a known issue? I'm guessing I should upgrade to mysql-4.12 now...
Jennifer already gave very relevant advice. I can add that Monty fixed a
crash in SHOW PROCESSLIST some 3 months ago. An u
at. In the long run that may help. Red Hat has a Bugzilla database, but it
did not work through my IExplorer browser. Maybe it works with Mozilla? Can
someone test?
> Thanks!
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http:/
be of a
> fixed length (for instance, a social security number)?
> I have a few tables with that problem/feature and
> because of that, instead of having fixed format rows I
> have dynamic ones. In a table with a few millions
> rows, it can make a big difference!
>
> tia
>
Wynne,
- Original Message -
From: "Wynne Crisman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "'Heikki Tuuri'" <[EMAIL PROTECTED]>
Sent: Friday, March 21, 2003 5:18 AM
Subject: Re: fulltext search
> Since InnoDB tables don't s
Florent,
Jon Frisby's DataDiff:
http://www.mrjoy.com/datadiff.shtml
"mysqldiff is a Perl script front-end to the CPAN module MySQL::Diff which
compares the data structures (i.e. table definitions) of two MySQL
databases"
http://adamspiers.org/computing/mysqldiff/
Best regards
?
we are still waiting for some customer to sponsor the porting.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL
Paul,
which MySQL version you are using?
http://www.innodb.com/ibman.html#InnoDB_foreign_keys
"
Corresponding ON UPDATE options are available starting from 4.0.8.
"
If you are using >= 4.0.8, can you create a small repeatable test case?
Best regards,
Heikki Tuuri
Innobase
Hi!
InnoDB is a MySQL table type which provides transactions, foreign key
constraints, and a non-free Hot Backup tool.
InnoDB is included in all versions of MySQL-4.0, which you can download from
http://www.mysql.com/downloads/mysql-4.0.html.
MySQL-4.0.12 is a bugfix release of the MySQL-4.0 bra
Hi!
InnoDB is a MySQL table type which provides transactions, foreign key
constraints, and a non-free Hot Backup tool.
InnoDB is included in MySQL-Max-3.23.56 which you can download from
http://www.mysql.com/downloads/mysql-3.23.html.
MySQL-Max-3.23 is the stable version which is recommended for
Paul,
- Original Message -
From: "Paul DuBois" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, March 17, 2003 1:05 AM
Subject: Re: Foreign Key and default action/RESTRICT behaviour?
> At 23:12
[ON UPDATE {CASCADE | SET NULL | NO ACTION
> | RESTRICT}]
>
> Is there a default action for ON DELETE and ON UPDATE if no action
> is specified in the database definition?
RESTRICT is, of course, the default 'action'. ON DELETE and ON UPDATE are
later additions.
...
Brandon,
thank you for the bug report. I will try to fix this in 4.0.xx.
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
See http://www.innodb.com for the online manual and latest news on InnoDB
sql query
- Original Message
uption is a Linux kernel problem that might help.
> I've placed the resolved stack trace and full error logs online at:
>
> http://www.oxyopia.com/~yi/stack.resolved
> http://www.oxyopia.com/~yi/failure.log
>
> TIA,
> --
> Yukari Iwatani
> <[EMAIL
s, you can look from the General Query Log
what SQL statements led to it.
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-4.0 from http://www.mysql.com
sql query
- Original Message -
From: "
Jan,
this is a design deficiency which was known to me, but was not documented. I
will remove it in some version 4.0.xx.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-4.0 from http
Philip,
> - Forwarded message from Philip Molter <[EMAIL PROTECTED]> -
>
> Date: Mon, 10 Mar 2003 08:30:22 -0600
> From: Philip Molter <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: InnoDB Assertion Error
>
> THE SITUATION:
> We're running MySQL 3.23.51. We have a table which has
tables and recreate the whole tablespace.
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-4.0 from http://www.mysql.com
sql query
- Original Message -
From: "Ask Bjoern Hansen" <[EM
l I complete the transaction that I started on my first window.
> Is this condition normal cos this works on both Oracle and Post gres.
>
> Regards
> Raghu
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb
an identical
> >machine (with identical setup and identical data, both without any
> >other load, both using /dev/sdaX with OS buffering), 3.23.51 took
> >longer for the same queries involving smaller table scans (0.26 vs.
> >0.17 seconds in mysql client). Not sure what's
20\#sql-268_2' to '.\transfer20\exrates2'
(errno: 150)
The ALTER TABLE you are trying to do would make some FOREIGN KEY
declarations not to obey the rules specified at
http://www.innodb.com/ibman.html#InnoDB_foreign_keys.
"
Similarly, if an ALTER TABLE fails and it refers t
: innodb deadlock leads to server crash
From: Heikki Tuuri
Date: Mon, 3 Mar 2003 10:42:48 +0200
Hi!
Ok, now I think I understand the problem. Since you use the -q option, the
client mysql retrieves rows in the result set in chunks of some size. As
InnoDB keeps the adaptive hash index latch S
InnoDB.
Thank you,
Heikki
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 10:24 AM
Subject: Re: innodb deadlock leads to server crash
> Hi!
>
> Your email address gives the error:
>
>
he fetches which:
mysql -q ... | program
executes take so long that InnoDB thinks the server has hung? How big is the
result set of your ORDER BY query in terms of rows and megabytes?
Regards,
Heikki
- Original Message -----
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[E
and might produce broken binaries.
I tried to repeat the hang in my computer, but did not succeed. Can you send
me what
SHOW CREATE TABLE ticketlast;
prints?
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
See http://www.innodb.com for
Keith,
please upgrade to 3.23.55. Your MySQL version is very old.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
sql query
- Original Message
Hi!
Some new information about the MySQL-4.0.10 compilation problem on Red Hat
8.0 (x86), but unfortunately no solution found yet, except running a MySQL
official binary you can download from www.mysql.com. A 4 day stress test of
an official binary ran fine.
One of MySQL AB employees said that on
Dyego,
- Original Message -
From: "Dyego Souza do Carmo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 10:42 PM
Subject: The MySQL and InnoDB FK´s
> Hi,
>
>I would like to know if is there a way to delete constraints
>witho
Dyego,
did you compile MySQL yourself and are using a debug version of mysqld?
The assertion is a DBUG_ASSERT which is only present in the debug version.
It fails because an earlier version of MySQL internally assigned a UNIQUE
key as the primary key of the table, but InnoDB was not aware of it.
David,
http://www.innodb.com/ibman.html#InnoDB_foreign_keys:
"Starting from 4.0.5 the InnoDB parser is aware of possible option
lower_case_table_names you give in my.cnf."
Upgrade to 4.0.11!
Heikki
Innobase Oy
sql query
...
Subject: Can't create FOREIGN KEY restraints on InnoDb ta
lease message but no other...
Lenz has not yet posted the general release note. You can look the changelog
from:
http://www.mysql.com/doc/en/News-4.0.11.html
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innod
query SELECT ... FROM ... ORDER BY
... DESC could hang in an infinite loop.
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http
Michael,
this is further evidence that the corruption last time was not a bug in the
insert buffer, but this is general Linux table corruption. I already
suggested that you should upgrade to Linux-2.4.20 or some other recent
kernel.
Please send me the full .err log. If you can keep the old corrup
Steff,
I am carbon copying this to [EMAIL PROTECTED] so that people see the
problem was probably found.
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTEC
Steff,
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, February 22, 2003 1:26 AM
Subject: Re: LOCK
Jungsu, Jeremy,
it can be considered as a bug that MySQL/InnoDB does not replicate the
setting
SET FOREIGN_KEY_CHECKS=0
I am working on fixing this bug in 4.0.x.
Regards,
Heikki
Innobase Oy
sql query
- Original Message -
From: ""Jeremy Tinley"" <[EMAIL PROTECTED]>
Newsgroups: mailing.
Ross,
- Original Message -
From: ""Ross Davis"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Saturday, February 22, 2003 12:14 AM
Subject: create fails with on delete set null
>
> Simply said this works:
> drop table if exists detail;
> create table detail
> (
> detail_i
ption_noticed) {
+ rec_sprintf(err_buf, 450, ibuf_rec);
+
+ fprintf(stderr,
+"InnoDB: Discarding record\n %s\n from the insert buffer!\n\n", err_buf);
-if (page) {
+} else if (page) {
/* Now we have at pcur a record which should be
inserted to the index page; NOTE that the call below
Michael,
how do I send you email? A 'Spamcop' seems to block email to you.
Regards,
Heikki
- Original Message -----
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: ""Michael T. Babcock"" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Se
Michael,
your database is probably corrupt.
The normal procedure in this case is to use the my.cnf option
set-variable=innodb_force_recovery=4
and dump your tables and recreate the whole tablespace.
But, please do not do that yet. I will send you a new version of
/mysql/innobase/ibuf/ibuf0ibu
Steff,
> We have our connection set to Autocommitt=1, and No table locks
> are ever explicitly being done on this table anyplace in any of our
> code modules.
in MySQL you have to do LOCK TABLES on EVERY table you use inside a LOCK
TABLES. You cannot lock just some table and use others unlocked.
Jeff,
MySQL does not have system tables from where you could query metadata with
ordinary SELECT queries. You have to use
SHOW CREATE TABLE tablename.
If you do not see your foreign key definitions in SHOW CREATE TABLE, then
you probably are using MyISAM tables, which do not support foreign keys
Jeff, Egor,
Guilhem Bichot just found a bug in replication of LOAD DATA LOCAL INFILE in
4.0.
The problem is the LOCAL keyword. Of a large import file, only 8 kB or 16 kB
will actually be replicated in the slave. Do you use the LOCAL keyword?
I do not know if the bug affects 3.23.
Are you using
omebody who knows what this is, and how I can get away from it?
Regards,
Ben.
.......
From: "Heikki Tuuri" ([EMAIL PROTECTED])
Subject: Re: Innodb table with auto-increment column doesn't create (err
1005)
View: Complete Thread (2 articles)
Original Format
Newsgroup
I think you should insist on the free aspect of mysql and it's simplicity
of
> use, because for somebody who knows the 2 databases, features wise,
> robustness wise and speed wise, interbase is far ahead of mysql.
Can you refer to some published benchmark where InterBase beats MySQL?
B
Hi!
I have the same problem in my new Red Hat 8.0 / Athlon 1.8 GHz laptop.
If I build MySQL-4.0.10 from source with
./BUILD/compile-pentium-debug
it crashes in installing MySQL system tables. If I use a MySQL binary distro
to install the system tables, then the mysqld I built may crash in
mysql
Martin,
this bug in multi-table UPDATE on InnoDB tables was reported 3 weeks ago and
Sinisa has fixed it to upcoming 4.0.11.
Regards,
Heikki
Innobase Oy
sql query
..
Subject: Bug? Update on 3 tables crashes in InnoDB
From: Martin Thoma
Date: Mon, 17 Feb 2003 11:57:12 +0100
Ca
7; AND SecondaryID = 'CKCBSBF2994311'
7 Query COMMIT
7 Query SET autocommit=1
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL
Steff,
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, February 13, 2003 7:21 PM
Subject: Re: Transaction problems using InnoDB, "not locked with LOCKTABLES"
> Heik
Mark, Steff,
- Original Message -
From: "Mark Matthews" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, February 12, 2003 3:09 AM
Subject: Re: Transaction problems using InnoDB, "not locked with LOCKTABLES"
> -BEGIN PGP SIGNED
,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
sql query
-
Before posting, please check:
http
Scott,
I would like to declare this as a 'feature'. You should not define multiple
foreign key constraints on the same foreign key/referenced key pair.
I could, of course, add an error message if someone tries to do that.
The algorithm in ON UPDATE CASCADE and ON DELETE CASCADE is this: InnoDB
t
Scott,
http://www.innodb.com/ibman.html#InnoDB_foreign_keys
"
Starting from version 3.23.50 you can also associate the ON DELETE CASCADE
or ON DELETE SET NULL clause with the foreign key constraint. Corresponding
ON UPDATE options are available starting from 4.0.8.
"
Regards,
Heikki
Innobase Oy
Sam,
I assume you are having the MySQL binlogging on? The following manual
excerpt explains why this has to work as it does:
"
INSERT INTO T SELECT ... FROM S WHERE ... sets an exclusive (non-next-key)
lock on each row inserted into T. Normally does the search on S as a
consistent read, but sets
te 100 times at 1 second intervals.
* Fixed a bug: SQL command REPLACE INTO t1 SELECT ... did not work if t1 has
an auto-inc column.
* An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in
the MySQL replication.
Best regards,
Heikki Tuuri
Innobase Oy
http://www.inno
Crescent,
if you look at the yourhostname.err file in the MySQL datadir, does it
contain anything?
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
See http://www.innodb.com for the online manual and latest news on InnoDB
sql query
add
another ibdata file.
> Need help.
>
> Shomal
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
sql query
--
InnoDB tablespace and
log files.
Support for multiple tablespaces in InnoDB is planned. You would have an
option to store every table in its own tablespace.
> Grover Cussi
> System Administrator
> www.cs.umss.edu.bo
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot bac
I do not know, but 4.1.0 might the the next in line.
> TIA
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://ww
Matthias,
what have you done? Below you create table 'foo' but mysql answers that it
cannot create 'stundenliste.frm'.
"
mysql> create table foo (id int auto_increment,unique key (id))
type=innodb;
ERROR 1005: Can't create table './test_smurf/stundenliste.frm' (errno: 121)
mysql> create table
Hi!
Over the past 2 years several users have complained about optimization of
queries of type
... WHERE col < x;
... WHERE col <= x;
... WHERE col > x;
... WHERE col >= x;
and, indeed, there was a major bug in the InnoDB query estimator. The fix
appears in 4.0.10 and 3.23.56.
"
MySQL/InnoDB-3.2
Anne,
- Original Message -
From: "Anne" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Monday, January 27, 2003 7:35 PM
Subject: Recover mysql database from hotbackup. This is Urgent!!!
> Hi,
>
> We are performing daily hotbackup of the mysql database using the
> script whi
tablespace end backup;
>
> alter tablespace begin backup;
>
> and so on for all tablespaces.
mysqldump is one.
InnoDB Hot Backup is a way to make binary backups whose restoration is
faster than table dumps.
> Thanks in advance.
>
> Enrico
Heikki Tuuri
Innobase Oy
-
Rogger,
- Original Message -
From: "Rogger Vasquez" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, January 24, 2003 4:43 PM
Subject: Re: MySQL/InnoDB-3.23.55 is released
&
Robert,
yes, if there are multiple UNIQUE keys in a table, then in the REPLACE
implementation there is a loop which DELETEs all records which have
conflicting UNIQUE key values.
Since you have kept the binlog of your database, you can rerun the SQL
statements and try to find where your rows magic
LATION. In synchronous
writes InnoDB now retries the write 100 times at 1 second intervals.
* An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in
the MySQL replication. The fix will appear in 4.0.11 and will probably not
be backported to 3.23.
Best regards,
Heikki Tuuri
In
Shashi,
please send these general MySQL questions to [EMAIL PROTECTED]
Thank you,
Heikki
sql query
- Original Message -
From: "N Shashidhara" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 24, 2003 7:37 AM
Subject: Column present in diffrent tables
> Dear Heikki,
Dyego,
- Original Message -
From: "Dyego Souza do Carmo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 23, 2003 10:35 PM
Subject: The diferences about /dev/hda1 and access via raw device
> Hi ! this question is very relevant for me !!!
>
>
>
- Original Message -
From: "Dyego Souza do Carmo" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Sent: Thursday, January 23, 2003 12:31 PM
Subject: Re[2]: Limitations of InnoDB about REPLICATION
> Dobrý den,
> quinta-feira, 23 de
Dyego,
- Original Message -
From: "Dyego Souza do Carmo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 23, 2003 12:13 PM
Subject: Limitations of InnoDB about REPLICATION
> Hello guy !
>
> The limitations about InnoDB on replication is present
Michael,
a good point. SET FOREIGN_KEY_CHECKS is currently not replicated properly.
I have to fix this by wrapping the SQL statement in the binlog inside
SET FOREIGN_KEY_CHECKS=0;
SET FOREIGN_KEY_CHECKS=1;
if thd->options & OPTION_NO_FOREIGN_KEY_CHECKS is true for the connection.
I hope the f
www.innodb.com/ibman.html#InnoDB_foreign_keys
> --
> For technical support contracts, goto https://order.mysql.com/?ref=ensita
> This email is sponsored by Ensita.net http://www.ensita.net/
>__ ___ ___ __
> / |/ /_ __/ __/ __ \/ /Victoria Reznichenko
>
ry' at a startup. In a regular startup these messages
are suppresses and you do not see them.
> query. sql
>
> --
> Chung Ha-nyung
> Sayclub <http://www.sayclub.com>
> NeoWiz <http://www.neowiz.com>
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB
n which is rolled
back. Thus, these are never replicated, and in the slave there should not be
any constraint violation errors.
> Sincerely
> Kris Karski
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign
> Do you think it's safe to (1) do the rename? or I'd better do a (2) import
> all to the new database? Which way is better?
RENAME is safe.
> Thank you,
> Jannie
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key suppor
ement: alter table _table_name_ disable keys;
> has any action on "INNODB" tables ?, helps improving bulk inserts ?.
no effect.
If you have UNIQUE secondary indexes, you can try
SET UNIQUE_CHECKS=0;
to speed up disk-bound inserts.
> thanx
>
> Carlos
Best regards,
Heikki T
Philip,
Jani promised that in February 2003 you can set autocommit=0 globally in
my.cnf.
I am carbon copying this to Jani. The feature is widely requested.
Regards,
Heikki
Subject: Disable autocommit by default
From: Philip Molter
Date: Thu, 16 Jan 2003 15:41:47 -0600
to age a bit.
In Windows NT/2000/XP unbuffered AIO seems to work ok, and provides better
performance than ordinary file IO.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http
adds appropriate
indexes to a set of CREATE TABLE statements where foreign keys are declared.
...
> how can i create the database without creating
> explicitly an index on each foreign keys of my
> database?
>
> any suggestions are appreciated.
> thanks to all.
Best regards,
He
ither deliberately or accidentally.
>
> Has anyone come across such a problem?
>
> (sql,query,database,odbc - spam block bypass)
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
See http://www.in
raint name
is not stored, and is not required by the FOREIGN KEY syntax, I think that
the syntax could be
ALTER TABLE frobboz DROP FOREIGN KEY (column1) REFERENCES abbaguu (column2);
> Muhammed
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.m
regards,
Heikki
Innobase Oy
sql query
- Original Message -
From: "Massimo Petrini" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Sent: Wednesday, January 15, 2003 9:13 AM
Subject: Re: problem to stop mysql under windows xp
> Nobody can h
Natale,
please address these general questions to [EMAIL PROTECTED]
InnoDB requires that the indexes are created explicitly. It would require a
change to MySQL to automate the creation of them.
Without indexes foreign key checks would be very slow because then every
check would have to do a tabl
files was >= 2 GB in a
32-bit computer, InnoDB would write log in a wrong position. That could make
crash recovery and InnoDB Hot Backup to fail.
* Fixed a bug: index cursor restoration could theoretically fail.
Best regards,
Heikki Tuuri
http://www.innodb.com
(For the mail filt
hen has stdout solely for its own use.
Regards,
Heikki
Innobase Oy
- Original Message -
From: "Matt Solnit" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Heikki Tuuri" <[EMAIL PROTECTED]>
Sent: Monday, January 13, 2003 9:26 PM
Subject: Disable log mes
is now fixed.
"
A general note: the bug list of MySQL is the changelog in the manual,
because it lists also upcoming releases. By looking there you often find the
explanation why some version does not work.
For InnoDB the bug list is http://www.innodb.com/ibman.html#InnoDB_history.
> Regar
stable 3.23.
If you want to emulate Oracle with different transaction isolation levels,
they are available starting from 4.0.5.
> R.T.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, dow
'. InnoDB does not accept the constraint because 'on delete
set null' is not sensible when you declare the column not null.
I have now added a note to InnoDB manuals about this.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key sup
r` char(1) default NULL,
-> PRIMARY KEY (`id_r`),
-> KEY `nip_h_index` (`nip_h`,`nrpok_p`)
-> ) TYPE=InnoDB;
Query OK, 0 rows affected (0.01 sec)
mysql>
mysql> alter table rezerwacje add foreign key (nip_h,nrpok_p) references
-> pokoje(nip_h,nrpok_p);
Query OK, 0 ro
`)
-> ) TYPE=InnoDB;
Query OK, 0 rows affected (0.01 sec)
mysql>
mysql> alter table rezerwacje add foreign key (nip_h,nrpok_p) references
-> pokoje(nip_h,nrpok_p);
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
mysql>
> --
> _/_/
t Solnit
> [EMAIL PROTECTED]
>
> P.S. This is just here to satisfy the spam filter: MySQL
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
og files in group=2 to get it to restart (a
suggestion by Heikki
> Tuuri)
If I try the wrong syntax, I get:
heikki@hundin:~/mysql-max-3.23.53a-pc-linux-gnu-i686/bin> mysqld
mysqld: unrecognized option `--innodb_log_files_in_group=3'
mysqld Ver 3.23.53a-max for pc-linux-gnu on
lock wait timeout.
* Fixed a bug: an assertion in btr0sea.c, in function
btr_search_info_update_slow could theoretically fail in a race of 3 threads.
* Fixed a bug: one could not switch a session transaction isolation level
back to REPEATABLE READ after setting it to something else.
Best regard
Hi!
A user of InnoDB Hot Backup just reported a bug. He has 3 InnoDB log files,
each 1 GB in size.
A 32-bit integer overflow can cause InnoDB to write log in a wrong offset.
That can spoil InnoDB recovery.
If you have too big log files, please follow the instructions at
http://www.innodb.com/ib
r case I think a
ROLLBACK is appropriate?
There is no method to unlock an InnoDB row during the transaction. That
feature could be added rather easily:
SELECT ... FROM ... WHERE ... UNLOCK;
but since such SQL commands do not exist in most other databases, I think
there is little need for the featur
er and the slave identical, though in the
master the statements are processed concurrently, while the slave processes
them in the serial order of the binlog. We say that the execution of SQL
statements is 'serializable', and the serialization order is the order in
which they are writt
umn in an index, InnoDB would
need to do a table scan of the parent table when you add a child row. That
is why you must have the column as the first column in an index, in both the
parent and the child table.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign
urself.
Jocelyn Fournier has done very valuable work by testing 4.1 in the past
months.
> Thanks
> Ahmed Farouk
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://ww
#x27;,
>epoch_inserted DATETIME NULL,
>modified_byVARCHAR(128) NOT NULL default 'root',
>epoch_modified DATETIME NULL,
>UNIQUE KEY keyword(id, username, uid),
>PRIMARY KEY (username,uid)
&g
y SHOW INNODB
STATUS, and picking the information you want? I can promise that the output
format of interesting stats will stay rather constant.
> Many thanks and Happy New Year to all!
The same to you!
> Jean-Luc
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and
fication to any office or public
> Phone: 540/675-3015, x225trust under the United States." -Article VI
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innod
701 - 800 of 1646 matches
Mail list logo
