Hello.
Have a look here:
http://dev.mysql.com/doc/refman/5.0/en/converting-tables-to-innodb.html
http://dev.mysql.com/doc/refman/5.0/en/innodb-restrictions.html
PaginaDeSpud wrote:
> i'm using myisam. Is there any tip i should know before to migrate this
> table to innodb ?
>
> Th
i'm using myisam. Is there any tip i should know before to migrate this
table to innodb ?
Thanks !
- Original Message -
From: "Gleb Paharenko" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, November 29, 2005 12:35 PM
Subject: Re: locking issues
Hello.
What table
Hello.
What table engine do you use for your tables? InnoDB usually
is the best choice if you have lots of concurrent updates and inserts.
"PaginaDeSpud" <[EMAIL PROTECTED]> wrote:
> I'm getting locking issues due to tables very often updated/insert.
>
> It's splitted into two tables,
Excuse me for late response.
When I do it from the mysql prompt it works fine but trough the API (I use
DAC for MySQL from microolap, maybe the bug is in there software!!) it
doesn't work fine.
I have try it on several versions: 4.1.1, 5.0.0 and 4.0.0.
Thank you for your help. If you think it
Hans van Dalen <[EMAIL PROTECTED]> wrote:
>
> A question about locking. In my code (delphi but that doesn't much matter)
> I fire ad-hoc queries (select). Before the query i fire a locking query
> (read) for that particular tables. Something like this:
>
> lock tables tab1 a read, tab2 b read
>
On Thursday 12 December 2002 14:06, Greg_Cope at sandwich dot pfizer dot com
wrote:
> I may be confused here but it would appear that when you issue a LOCK
> TABLES tbl_name { READ|WRITE }; You cannot read from another unlocked table
> in the same connection eg:
>
> mysql> LOCK TABLES users read
At 19:52 + 12/9/02, [EMAIL PROTECTED] wrote:
Hi All,
I may be confused here but it would appear that when you issue a LOCK TABLES
tbl_name { READ|WRITE }; You cannot read from another unlocked table in the
same connection eg:
You're supposed to lock all the tables that you'll need until you
