Hi,
I want to access data from an InnoDB table. I know that I can do this using
the corresponding handler and ha_rnd_next() or ha_index_next().
My problem is that the original MySQL code is outperforming my
implementation even on simple projection queries, even though I use the same
functions.
T
Hi, I have a fairly small (data dir is 1.2GB) InnoDB database managed
by MySQL 5.4.3-beta on an 8-core x86_64 Linux box with 16GB RAM. I'd
like to use as much of the memory as possible, but despite specifying
(e.g.) --innodb-buffer-pool-size=30, mysql only ever takes up
374M of resident mem
-
> From: Néstor
> Date: Mon, 14 Sep 2009 07:44:25
> To:
> Subject: HOW TO Backup a mysql innodb on windows?
>
> Maybe one of you experts know the answer.
>
> I have a Innodb database that I want to back up. Is there a free tool to
> do this?
> mysqlhotbackup is a p
ia's No. 1 Network. Go
>>> for it!
>>>
>>> -Original Message-
>>> From: Néstor
>>> Date: Mon, 14 Sep 2009 07:44:25
>>> To:
>>> Subject: HOW TO Backup a mysql innodb on windows?
>>>
>>> Maybe one of you expe
On Mon, Sep 14, 2009 at 8:28 AM, Michael Dykman wrote:
> If I may,
>
> If you have foreign keys on your InnoDB, you can still import your
> data to MyISAM but foreign keys will be lost. Otherwise, the data
> will load just fine.
Very good point. My comment was based on the possibly erroneous
as
If I may,
If you have foreign keys on your InnoDB, you can still import your
data to MyISAM but foreign keys will be lost. Otherwise, the data
will load just fine.
- michael dykman
On Mon, Sep 14, 2009 at 11:14 AM, Todd Lyons wrote:
> On Mon, Sep 14, 2009 at 7:44 AM, Néstor wrote:
>> Maybe o
k. Go for
>> it!
>>
>> -Original Message-
>> From: Néstor
>> Date: Mon, 14 Sep 2009 07:44:25
>> To:
>> Subject: HOW TO Backup a mysql innodb on windows?
>>
>> Maybe one of you experts know the answer.
>>
>> I have a Innodb databa
On Mon, Sep 14, 2009 at 7:44 AM, Néstor wrote:
> Maybe one of you experts know the answer.
>
> I have a Innodb database that I want to back up. Is there a free tool to
> do this?
> mysqlhotbackup is a paid tool, is that the only one available?
You can also use the free tool from Percona which c
Maybe one of you experts know the answer.
I have a Innodb database that I want to back up. Is there a free tool to
do this?
mysqlhotbackup is a paid tool, is that the only one available?
If I do a mysqldump of the innodb databse, will I be avail to uploaded into
a myisam
database and will it wo
A mysqldump will work just fine. By default, that dump is going to
explicitly specify the table type .. you will have to edit it if you
want to import to MyISAM.
- michael dykman
On Mon, Sep 14, 2009 at 10:44 AM, Néstor wrote:
> Maybe one of you experts know the answer.
>
> I have a Innodb d
Bryan Cantwell wrote:
I have Mysql 5.0.45 using innodb tables.
Occasionally, I get corrupted tables. I can go into Mysql administrator
gui and see the bad table and I can repair the index or whatever is
wrong from the gui.
I need a command line way to periodically detect for issues and if it
find
I have Mysql 5.0.45 using innodb tables.
Occasionally, I get corrupted tables. I can go into Mysql administrator
gui and see the bad table and I can repair the index or whatever is
wrong from the gui.
I need a command line way to periodically detect for issues and if it
finds one the I need a comma
Depending on the version you use MySQL will see a definition of
varchar(25) as 25 bytes or 25 characters. I believe this changed from
4.1 to 5.0 respectively but I am not sure.
THis could be the root of the problem
Boyd
CONFIDENTIALITY NOTICE: This email & attached documents may conta
On 3/26/07, Anil D <[EMAIL PROTECTED]> wrote:
Varchar = 0 bytes
I don't think this is right, see below.
Charset used: UTF8
UTF8 means that some characters may be two bytes, see below.
Note: When consider even the size Varchar(m) = m+1 bytes, the size of row
has reached 35,000 bytes.
Hey all. Well I just finished my first version of a little tool I have
affectionately dubbed "dumpster".
I do use my own SQL wrapper functions, but they should map fairly cleanly to
a search and replace for the stock PHP mysql_*() ones, or your own ones.
Mad props to Peter Brawley [EMAIL PROTEC
On Sunday, May 07, 2006 6:14 PM, Greg 'groggy' Lehey wrote:
> On Sunday, 7 May 2006 at 9:27:31 -0700, Robert DiFalco wrote:
>> What are people doing for backups on very large MySQL/InnoDB
>> databases? Say for databases greater than 200 GB. Curious about
>> the
---
-Original Message-
From: Duzenbury, Rich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 9 May 2006 6:39 AM
To: mysql@lists.mysql.com
Subject: RE: Backups with MySQL/InnoDB
> -Original Message-
> From: Daniel da
> -Original Message-
> From: Daniel da Veiga [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 08, 2006 1:55 PM
> To: mysql@lists.mysql.com
> Subject: Re: Backups with MySQL/InnoDB
>
> On 5/8/06, David Hillman <[EMAIL PROTECTED]> wrote:
> > On May 7, 2006,
On 5/8/06, David Hillman <[EMAIL PROTECTED]> wrote:
On May 7, 2006, at 11:29 PM, Robert DiFalco wrote:
> Fast, incremental, compressed, and no max-size limitations. Must be
> transaction safe; able to run while transactions are going on without
> including any started after the backup began; the
On May 7, 2006, at 11:29 PM, Robert DiFalco wrote:
Fast, incremental, compressed, and no max-size limitations. Must be
transaction safe; able to run while transactions are going on without
including any started after the backup began; the usual stuff.
Incremental, transaction safe, compresse
nt: Sunday, May 07, 2006 6:14 PM
To: Robert DiFalco
Cc: mysql@lists.mysql.com
Subject: Re: Backups with MySQL/InnoDB
On Sunday, 7 May 2006 at 9:27:31 -0700, Robert DiFalco wrote:
> What are people doing for backups on very large MySQL/InnoDB
databases?
> Say for databases greater than 200 G
On Sunday, 7 May 2006 at 9:27:31 -0700, Robert DiFalco wrote:
> What are people doing for backups on very large MySQL/InnoDB databases?
> Say for databases greater than 200 GB. Curious about the backup methods,
> procedures, and frequency.
A second question, but not for the first
What are people doing for backups on very large MySQL/InnoDB databases?
Say for databases greater than 200 GB. Curious about the backup methods,
procedures, and frequency.
?22,74279,74279#msg-74279
I need explanation about this issue :)
Heikki Tuuri wrote:
Ady,
- Original Message - From: "Ady Wicaksono"
<[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, March 06, 2006 5:32 PM
Subject: MySQL InnoDB Row insert Calculation
W
base.myodbc
Sent: Monday, March 06, 2006 5:32 PM
Subject: MySQL InnoDB Row insert Calculation
With autocommit=1, anybody could give calculation on how many rows could
be inserted in 1 seconds?
I am assuming that you perform a COMMIT after each insert.
If the computer does not have a battery-b
Ady,
- Original Message -
From: "Ady Wicaksono" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, March 06, 2006 5:32 PM
Subject: MySQL InnoDB Row insert Calculation
With autocommit=1, anybody could give calculation on how many rows could
be inser
With autocommit=1, anybody could give calculation on how many rows could
be inserted in 1 seconds?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hi!
- Original Message -
From: <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, February 14, 2006 5:50 PM
Subject: MySql InnoDB
Hi,
I'v installed MySql on my machine and created a new tables.
when i open some table to alter it,i see in the COMM
Ok greg,
I'll report this bug
Thx
Greg 'groggy' Lehey wrote:
On Wednesday, 16 November 2005 at 20:40:35 +0700, Ady Wicaksono wrote:
I have MySQL with about 12 billion rows when i try to create 2
process, each select count(*) on the same table after a long
time about 30 minutes it crash
On Wednesday, 16 November 2005 at 20:40:35 +0700, Ady Wicaksono wrote:
> I have MySQL with about 12 billion rows when i try to create 2
> process, each select count(*) on the same table after a long
> time about 30 minutes it crashed :(
>
> ANy information?
>
> ...
>
> InnoDB: We intentionally
Dear All
It happens after these condition
InnoDB: ## Diagnostic info printed to the standard error stream
InnoDB: Warning: a long semaphore wait:
--Thread 1103972416 has waited at ../include/btr0btr.ic line 28 for
369.00 seconds the semaphore:
S-lock on RW-latch at 0x88cdd6b8 created in fi
I have MySQL with about 12 billion rows
when i try to create 2 process, each select count(*) on the same
table after a long time about 30 minutes
it crashed :(
ANy information?
Log file :
051116 20:27:22InnoDB: Assertion failure in thread 2366216768 in file
srv0srv.c line 1873
InnoDB: W
deadlocks.
Bugs fixed:
* Do very fast shutdown only if innodb_fast_shutdown=2, but wait for threads
to exit and release allocated memory if innodb_fast_shutdown=1. Starting
with MySQL/InnoDB 5.0.5, InnoDB would do brutal shutdown also when
innodb_fast_shutdown=1. (Bug #9673)
* Fixed Inn
Hi!
InnoDB is the MySQL table type that supports foreign key constraints,
transactions, two-phase commit in XA, row-level locking, non-locking
consistent read (MVCC), all four SQL-1992 isolation levels of transactions,
multiple tablespaces, asynchronous unbuffered disk I/O on Windows, and a
n
Hi,
the only right answers sould be here :
http://www.mysql.com/company/legal/licensing/
Mathias
Selon Daniel Kiss <[EMAIL PROTECTED]>:
> Hi All,
>
> I would have a question about licensing MySQL.
>
> I am writing an application that relies on MySQL+InnoDB (uses MySQL as
Hi,
the only right answers sould be here :
http://www.mysql.com/company/legal/licensing/
Mathias
Selon Daniel Kiss <[EMAIL PROTECTED]>:
> Hi All,
>
> I would have a question about licensing MySQL.
>
> I am writing an application that relies on MySQL+InnoDB (uses MySQL as
m writing an application that relies on MySQL+InnoDB (uses MySQL as a
> > database backend). I will distribute my program under GPL (get fees only
> > for official support). Do I or my client have to buy MySQL+InnoDB
> > licenses in this case?
> >
> > Thank you,
> &g
Hi All,
I would have a question about licensing MySQL.
I am writing an application that relies on MySQL+InnoDB (uses MySQL as a
database backend). I will distribute my program under GPL (get fees only
for official support). Do I or my client have to buy MySQL+InnoDB
licenses in this case
Hi!
Greetings to all from the MySQL Users Conference 2005 in Santa Clara! The
conference has just kicked off with tutorials, and will last till Thursday.
Close to 1000 people are expected to attend the conference.
MySQL-5.0 is probably the most important new MySQL release in several years.
On t
Hi!
MySQL/InnoDB-4.1.11 is a bugfix release of the stable 4.1 branch. This
branch is recommended for production use. There are no important bug fixes
in 4.1.11, for most users there is no need to upgrade from 4.1.10.
InnoDB is the MySQL table type that supports foreign key constraints
fault. This typically saves 20 % of space
compared to the old InnoDB table format. Note that the old tables that you
have will still have the old table format. There is no automatic conversion
when you upgrade to 5.0.3. New tables will by default have the new table
format.
* MySQL/InnoDB now sup
Hi!
InnoDB is the MySQL table type that supports FOREIGN KEY constraints,
transactions, row-level locking that is never escalated, multiversioned
concurrency control, asynchronous unbuffered disk I/O on Windows, and a
non-free online hot backup tool. InnoDB is an 'ACID'-compliant table type.
In
Hello.
> How to force to kill process which make lock of table ? since PHP make
> many persistent connection to MySQL and i don't know
> which one is locking the table :(
You may get information about processes on your MySQL server using SHOW
PROCESSLIST
and kill the weird process with th
I have an PHP that do application
$sql = "SET AUTOCOMMIT=0";
$db->execQuery($sql);
$sql = "DELETE FROM TABLE X WHERE...";
if($db->execQuery($sql)){
print "ERROR ";
exit(0);
}
$sql = "INSERT INTO TABLE ";
if($db->execQuery($sql)){
print "ERROR ";
exit(0);
}
I have a persistent conne
Innobase Oy declares MySQL/InnoDB-4.1 stable
Innobase Oy has decided to declare MySQL/InnoDB-4.1 stable and recommended
for all production use, starting from version 4.1.10. MySQL/InnoDB-4.1 has
been out for almost two years now, there have been millions of downloads of
the software, and it is
Asad,
InnoDB type tables have enforced FOREIGN KEY constraints since 2001.
Unfortunately, none of the table types of MySQL yet supports CHECK
constraints.
Best regards,
Heikki
.
List: mysql
Subject:Re: MySQL/InnoDB-4.1.10 is released
From: Asad Habib
Date
f option innodb_file_per_table should upgrade to
> this version, because this fixes the bug introduced to the Windows version
> of 4.1.9, and earlier versions contained the critical bug in
> innodb_file_per_table.
>
>
> Functionality added or changed:
>
> * When MySQL/Inno
n1 non-BINARY indexed
columns in MySQL versions <= 4.1.2, then you have to rebuild those tables
after you upgrade to >= 4.1.3. The reason is that the sorting order of those
characters and the space character changes for some character sets in 4.1.3.
See the MySQL/InnoDB-4.1.3 changelog f
Nick,
- Original Message -
From: "Nick Arnett" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, January 14, 2005 9:28 PM
Subject: Re: MySQL/InnoDB-4.1.9 is released
Heikki Tuuri wrote:
http://dev.mysql.com/doc/mysql/en/LOCK_TABLES.html
"
The co
Heikki Tuuri wrote:
http://dev.mysql.com/doc/mysql/en/LOCK_TABLES.html
"
The correct way to use LOCK TABLES with transactional tables, like
InnoDB, is to set AUTOCOMMIT = 0 and not to call UNLOCK TABLES until
you commit the transaction explicitly. When you call LOCK TABLES,
InnoDB internally tak
Nick,
- Original Message -
From: "Nick Arnett" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, January 14, 2005 7:39 PM
Subject: Re: MySQL/InnoDB-4.1.9 is released
Heikki Tuuri wrote:
* Do not acquire an internal InnoDB table lock in LOCK TABLES
Heikki Tuuri wrote:
* Do not acquire an internal InnoDB table lock in LOCK TABLES if
AUTOCOMMIT=1. This helps in porting old MyISAM applications to InnoDB.
InnoDB table locks in that case caused very easily deadlocks.
Could you explain a bit more about how this relates to MyISAM? Is it
just tha
u have to rebuild those tables
after you upgrade to >= 4.1.3. The reason is that the sorting order of those
characters and the space character changes for some character sets in 4.1.3.
See the MySQL/InnoDB-4.1.3 changelog for a precise description of the cases
where you need to rebuild the
Hi!
InnoDB is the MySQL table type that supports transactions, FOREIGN KEY
constraints, row-level locking, non-locking consistent reads, and a non-free
Hot Backup utility.
Release 4.0.23 is a bugfix release of the stable MySQL-4.0 branch. This
release fixes the critical hang bug of mysqld in My
and the space character changes for some character sets in 4.1.3.
See the MySQL/InnoDB-4.1.3 changelog for a precise description of the cases
where you need to rebuild the table. Also MyISAM tables have to be rebuilt
or repaired in these cases.
* If you have used column prefix indexes on UTF-8 co
Walt,
- Original Message -
From: "kernel" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, December 02, 2004 11:01 PM
Subject: Re: MySQL/InnoDB-5.0.2 is released
"MySQL to return wrong results if a SELECT uses two indexes at the same
time&qu
he
sorting order of those characters and the space character changes for
some character sets in 4.1.3. See the MySQL/InnoDB-4.1.3 changelog for
a precise description of the cases where you need to rebuild the
table. Also MyISAM tables have to be rebuilt or repaired in these cases.
* If you have used c
I(32) to non-latin1 non-BINARY indexed
columns in MySQL versions <= 4.1.2, then you have to rebuild those tables
after you upgrade to >= 4.1.3. The reason is that the sorting order of those
characters and the space character changes for some character sets in 4.1.3.
See the MySQL/InnoDB-4
Hi!
InnoDB is the MySQL table type that supports FOREIGN KEY constraints,
row-level locking, Oracle-style consistent, non-locking SELECTs, multiple
tablespaces (in 4.1), and a non-free online hot backup tool.
Release 4.0.22 is mainly a bugfix release of the stable 4.0 series. This
release fixes
characters < ASCII(32) to non-latin1 non-BINARY indexed
columns in MySQL versions <= 4.1.2, then you have to rebuild those tables
after you upgrade to >= 4.1.3. The reason is that the sorting order of those
characters and the space character changes for some character sets in 4.1.3.
Se
Hi!
InnoDB is a MySQL table type which supports FOREIGN KEY constraints,
row-level locking, Oracle-style consistent, non-locking SELECTs, multiple
tablespaces, and a non-free online hot backup tool.
Release 4.1.6 is mainly a bugfix release. We do not yet declare
MySQL/InnoDB-4.1 stable, because
tin1 non-BINARY indexed
columns in MySQL versions <= 4.1.2, then you have to rebuild those tables
after you upgrade to >= 4.1.3. The reason is that the sorting order of those
characters and the space character changes for some character sets in 4.1.3.
See the MySQL/InnoDB-4.1.3 changelog for
key
constraints: long chains of cascaded operations would cause a stack overflow
and crash the server. Cascaded operations are now limited to 15 levels. (Bug
#4446)
* Fixed a possible bug in LOCK TABLES introduced in MySQL/InnoDB-4.0.19: The
count of tables explicitly locked by a transaction was incremente
Hi!
InnoDB is a MySQL table type that provides foreign key constraints, ACID
transactions, row-level locking, consistent (MVCC) non-locking reads,
transaction savepoints, and a commercial InnoDB Hot Backup tool to MySQL.
InnoDB is included in all MySQL releases, except the commercial '
.
Nickolai
-Oprindelig meddelelse-
Fra: Nickolai Nielsen [mailto:[EMAIL PROTECTED]
Sendt: 10. juli 2004 16:28
Til: [EMAIL PROTECTED]
Emne: SV: MySQL/InnoDB crashes system
Hi
I still got this freeze problem, i have found out that this bug is related
to InnoDB, i converted the table that
996B Gigabit NIC
The servers have SP4 and all updates
if anyone have an idea on how to troubleshoot this?
Thanks
Nickolai Nielsen
-Oprindelig meddelelse-
Fra: Heikki Tuuri [mailto:[EMAIL PROTECTED]
Sendt: 9. juli 2004 05:07
Til: [EMAIL PROTECTED]
Emne: Re: MySQL/InnoDB crashes system
"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, July 08, 2004 8:33 PM
Subject: MySQL/InnoDB crashes system
> hi
>
> this SQL frezes the system:
> SELECT * FROM journal into OUTFILE 'c:/Backup/current/journal.asc' FIELDS
> terminated by &#
hi
this SQL frezes the system:
SELECT * FROM journal into OUTFILE 'c:/Backup/current/journal.asc' FIELDS
terminated by '|' LINES terminated by '\r\n'
this started after the table was converted to InnoDB, usualy it runs normaly
the first time, but on 2-5 run it frezes the system so i have to reboo
Milan Svrlo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'd ask you :
> Can I use in MySQL 4.x on InnoDB tables something like :
> create dump from this InnoDB tables with cascade INSERT sql statements
> based foreign keys ?
> And if yes, how ?
>
No.
Probably you need mysqldump and SET FOREIGN_KEY_CHE
Hi,
I'd ask you :
Can I use in MySQL 4.x on InnoDB tables something like :
create dump from this InnoDB tables with cascade INSERT sql statements
based foreign keys ?
And if yes, how ?
thank you very much
regards
Milan Svrlo
-=x=-
Skontrolované antivírovým programom NOD32
--
MySQL General Mailing
/doc/mysql/en/InnoDB_foreign_key_constraints.html
The complete changelog of 4.1.2:
Functionality added or changed:
* Support multiple character sets. Note that tables created in other
collations than latin1_swedish_ci cannot be accessed in MySQL/InnoDB 4.0.
* Automatically create a suitable index
On Tue, May 18, 2004 at 10:56:14PM +0200, Mark wrote:
> Mihail Manolov wrote:
>
> >>> Release 4.0.20 is mainly a bugfix release, but there are also some
> >>> important functional changes. Release 4.0.19 was completely skipped
> >>> over because Bug #3596 might have caused segmentation faults on s
Mihail Manolov wrote:
>>> Release 4.0.20 is mainly a bugfix release, but there are also some
>>> important functional changes. Release 4.0.19 was completely skipped
>>> over because Bug #3596 might have caused segmentation faults on some
>>> platforms. The changelog below lists all the changes sin
i" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, May 18, 2004 2:21 PM
Subject: Re: MySQL/InnoDB-4.0.20 is released
> Heikki Tuuri wrote:
>
> > Release 4.0.20 is mainly a bugfix release, but there are also
some
> > important fu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark wrote:
| Heikki Tuuri wrote:
|
|
|>Release 4.0.20 is mainly a bugfix release, but there are also some
|>important functional changes. Release 4.0.19 was completely skipped
|>over because Bug #3596 might have caused segmentation faults on some
|>pla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark wrote:
| Heikki Tuuri wrote:
|
|
|>Release 4.0.20 is mainly a bugfix release, but there are also some
|>important functional changes. Release 4.0.19 was completely skipped
|>over because Bug #3596 might have caused segmentation faults on some
|>pla
Heikki Tuuri wrote:
> Release 4.0.20 is mainly a bugfix release, but there are also some
> important functional changes. Release 4.0.19 was completely skipped
> over because Bug #3596 might have caused segmentation faults on some
> platforms. The changelog below lists all the changes since 4.0.18.
Hi!
InnoDB is a MySQL table type that provides FOREIGN KEY constraints,
transactions, row level locking and multiversioned concurrency control to
MySQL, as well as a commercial hot backup tool.
Release 4.0.20 is mainly a bugfix release, but there are also some important
functional changes. Releas
On Fri, 16 Apr 2004, mayuran wrote:
> I would like to optimize the configuration settings
> for this beast of a machine, here are the specs:
>
> Quad Xeon 3ghz (4x2 = 8 cpus), 512 cache
> 16 gigs ram
> running Redhat Enterprise 3.0 AS
> All tables are InnoDB.
>
> I read this warning in the MySQL d
I would like to optimize the configuration settings
for this beast of a machine, here are the specs:
Quad Xeon 3ghz (4x2 = 8 cpus), 512 cache
16 gigs ram
running Redhat Enterprise 3.0 AS
All tables are InnoDB.
I read this warning in the MySQL documentation:
*Warning:* On GNU/Linux x86, you must be
Has anyone had any luck getting MySQL 4.0.18 (specifically
innodb_buffer_pool_size) to use large amounts of memory on a G5 running
OS X Server 10.3.3?
I initially tried with the MySQL built binary, and was unable to get
innodb_buffer_pool_size to go beyond 1.5 GB. Here's the my.cnf section
that a
I have a problem with mysql/innodb, hopefully someone
here can offer a nice pointer.
our innodb databases got wiped out (oops), and the problem
is the .frm files dont seem to match the structure needed,
we tried working around that in the docs online, but now
we get this message:
InnoDB: Error
I have a problem with mysql/innodb, hopefully someone
here can offer a nice pointer.
our innodb databases got wiped out (oops), and the problem
is the .frm files dont seem to match the structure needed,
we tried working around that in the docs online, but now
we get this message:
InnoDB: Error
Hi!
InnoDB is a MySQL table type which provides transactions, row-level locking,
foreign key constraints, and a non-free hot backup tool for backing up
InnoDB tables.
InnoDB is included in all MySQL-4.0, 4.1, and 5.0 downloads, and also in the
MySQL Pro commercial, non-GPL MySQL license.
Release
Ramesh,
- Alkuperäinen viesti -
Lähettäjä: "Ramesh Vadlapatla" <[EMAIL PROTECTED]>
Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]>
Lähetetty: Monday, December 29, 2003 10:48 PM
Aihe: Re: MySQL/InnoDB-5.0.0 is released
> Hello Heikki,
>
>
Hi!
Due to Christmas, this release note comes late.
For MySQL users release 5.0.0 is a milestone: you can now write stored
procedures in MySQL.
InnoDB in this MySQL release is essentially the same as in 4.1.1, with the
bug fixes of 4.0.17 included. Later 5.0.x versions will probably include new
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - hot backup tool for InnoDB which also backs up MyISAM
tables
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: ""Dmitry Anikin"" <[EMAIL
evel
locking, multiversioned concurrency control, and foreign key constraints. An
separate online binary hot backup tool for InnoDB can be bought from
http://www.innodb.com/order.php.
...
The MySQL/InnoDB version 4.0 is the stable version which is recommended for
production use. Release 4.0.17 of In
mos wrote:
At 01:14 AM 12/16/2003, you wrote:
mos wrote:
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a
classic deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which
we will call R1.
2. Transaction B obtains an
At 01:14 AM 12/16/2003, you wrote:
mos wrote:
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a classic
deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we
will call R1.
2. Transaction B obtains an exclusive lo
mos wrote:
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a
classic deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we
will call R1.
2. Transaction B obtains an exclusive lock on another set of rows
which we
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a classic
deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we will
call R1.
2. Transaction B obtains an exclusive lock on another set of rows which we
will call R2
To elaborate on Dr Frank's thing if you're interested, here's a classic
deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we
will call R1.
2. Transaction B obtains an exclusive lock on another set of rows which
we will call R2.
3. Transaction A requests (but ob
Hi,
Dmitry Anikin schrieb:
>
> Suppose some user issued 'select ... for update', then
> went for coffee-break (to think hard on what he
> really wants to update in that row). Another client
> tries to update the same row and I don't want him to
> wait, just immediately return an error, so he coul
Suppose some user issued 'select ... for update', then
went for coffee-break (to think hard on what he
really wants to update in that row). Another client
tries to update the same row and I don't want him to
wait, just immediately return an error, so he could
do some other useful task meanwhile. I
Hi!
The long-awaited MySQL/InnoDB-4.1.1 has been released. It is still labeled
as alpha, because there are so many new features and bug fixes in it
compared to 4.1.0.
IMPORTANT NOTE: if you upgrade to InnoDB-4.1.1, you cannot downgrade any
more! That is because earlier versions of InnoDB are not
Hello all,
Default optimizer behavior has changed in 4.0.16 (since 4.0.14)
for this simple question:
select state_id, orderdata_id from order_delivery where
orderdata_id in
(3193340,3193343,3193346,3193349,3193352,3193355)
and is_deleted=0 order by xtime desc
CREATE TABLE `order_delivery` (
`o
Gabriel,
- Original Message -
From: "Gabriel Ricard" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, October 27, 2003 6:46 PM
Subject: InnoDB on Raw partitions in OSX (was Re: MySQL/InnoDB-4.0.16 is
released + sneak peek of 4.1.1)
> On Monday, O
On Monday, October 27, 2003, at 07:45 AM, Chris Nolan wrote:
2. I personally use ReiserFS for all of my stuff, most of which is
based upon InnoDB. One thing you have to remember is that InnoDB
treats the space inside the tablespace as a Berkeley Fast
Filesystem-style space, using the underlayin
ournaled file system extra overhead? If so, is
Raw significantly more efficient? How does this choice effect backup
soultion?
thanks, Jon
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 24, 2003 9:55 PM
Sub
1 - 100 of 308 matches
Mail list logo
