Hi!
Tobias Hi!
Tobias I'm in the same position as Steve: Considering switching from MyISAM to InnoDB
because of the
Tobias row-level locking capabilities. My application has quite a lot of
updates/inserts mixed with
Tobias selects, and is starting to suffer from the table-locking policy...
: InnoDB frightens me...
Hi!
Tobias Hi!
Tobias I'm in the same position as Steve: Considering switching from MyISAM to
InnoDB because of
the
Tobias row-level locking capabilities. My application has quite a lot of
updates/inserts mixed
with
Tobias selects, and is starting to suffer from
: [EMAIL PROTECTED]
Subject: Re: InnoDB frightens me...
Thanks - that would be great!
I'm sure a lot of people will find this very helpful.
Regards,
Tobias
- Original Message -
From: Michael Widenius [EMAIL PROTECTED]
To: Tobias Lind - Telia Internet [EMAIL PROTECTED]
Cc
on replication issues.
Steve Rapaport.
] -Original Message-
] From: Tobias Lind - Telia Internet [mailto:[EMAIL PROTECTED]]
] Sent: Tuesday, March 05, 2002 1:46 PM
] To: [EMAIL PROTECTED]
] Cc: [EMAIL PROTECTED]
] Subject: Re: InnoDB frightens me...
]
]
] Thanks - that would be great!
] I'm
On Tue, Mar 05, 2002 at 09:58:13PM +0100, Steve Rapaport wrote:
I sure would, thanks Monty and Tobias. In particular some sample
update/insert/delete db code for MyISAM vs. InnoDB, (especially in
the case where you're not adding transactions, just trying to take
advantage of row-locking.)
- Telia Internet; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: InnoDB frightens me...
On Tue, Mar 05, 2002 at 09:58:13PM +0100, Steve Rapaport wrote:
I sure would, thanks Monty and Tobias. In particular some sample
update/insert/delete db code for MyISAM vs. InnoDB, (especially in
the case
Hi!
I'm in the same position as Steve: Considering switching from MyISAM to InnoDB because
of the
row-level locking capabilities. My application has quite a lot of updates/inserts
mixed with
selects, and is starting to suffer from the table-locking policy...
And like Steve, I'm also scared! :)
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, March 03, 2002 6:46 AM
Subject: Re: InnoDB frightens me...
Steve,
I added an item to the TODO list at http://www.innodb.com/todo.html
..
May, 2002:
Make a data file auto-extendible. You can specify the last data file
On Mon, Mar 04, 2002 at 09:30:16AM -0500, Ken Menzel wrote:
Hi Heikki,
I don't know if this has been requested, but what about a tool to
'pre-create' dataspace? This tool would allow someone to create a
new dataspace, then a quick restart (After adding the name of the
space to 'my.cnf')
On Monday 04 March 2002 09:32 pm, you wrote:
On Mon, Mar 04, 2002 at 09:30:16AM -0500, Ken Menzel wrote:
Hi Heikki,
I don't know if this has been requested, but what about a tool to
'pre-create' dataspace? This tool would allow someone to create a
new dataspace, then a quick restart
Steve,
I added an item to the TODO list at http://www.innodb.com/todo.html
..
May, 2002:
Make a data file auto-extendible. You can specify the last data file in
innodb_data_file_path like this:
ibdata1:50Mautoextend
It will create a data file whose initial size is 50 MB, and InnoDB will
On Sat, Mar 02, 2002 at 11:14:42PM +0100, Steve Rapaport wrote:
I'm seriously considering switching to mysql-max so I can make my
session handling table an Innodb type. Currently the mysql locking
policy allows big traffic jams when several sessions are active
simultaneously, and it's the
On Sat, Mar 02, 2002 at 06:52:57PM -0800, Jeff Kilbride wrote:
I'm looking to make the move to InnoDB, too. All I've heard is positve.
Here's a reply I got on another list:
If you have a very busy read/write op database, MyISAM can't handle
it. It's very efficient
...
I may have posted the same question here, earlier. I'd appreciate any input.
Thanks,
--jeff
- Original Message -
From: Jeremy Zawodny [EMAIL PROTECTED]
To: Jeff Kilbride [EMAIL PROTECTED]
Cc: MySQL [EMAIL PROTECTED]
Sent: Saturday, March 02, 2002 7:11 PM
Subject: Re: InnoDB
14 matches
Mail list logo
