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.
>
>
I'm getting locking issues due to tables very often updated/insert.
It's splitted into two tables, one has the more updated data and the another
has the more static data. I'm using queries with JOIN, would it be better
for performance to use two queries instead of using JOIN?
Hi,
I'm running quite a large database - mostly inserts (4-5 million rows a day)
and an occasional select to generate some report based on the inserted data
which works very well.
Once a month I need to generate a larger number of reports. The SELECT queries
are optimized quite well but some of
Hello List,
Recently I needed to alter a large innodb table (~200k rows) to add a
column on a live server. The alter table ran fine on the development
server with close to the same number of rows in the table so I didn't
anticipate too much trouble. The list archive and the documentation
indicate
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
>
Hi Group,
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
(execute)
select * from tab1 a, tab2 b where.
[EMAIL PROTECTED]
> - Original Message -
> From: "Jeff Snoxell" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, December 12, 2002 6:57 PM
> Subject: More locking issues
>
> > Hi,
> >
> > I'm new to MySQL. I see
ssage -
From: "Michael T. Babcock" <[EMAIL PROTECTED]>
To: "Gelu Gogancea" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "Jeff Snoxell" <[EMAIL PROTECTED]>
Sent: Thursday, December 12, 2002 8:44 PM
Subject: Re: More locking issues
> Gelu Go
Gelu Gogancea wrote:
If you have more than one user connected to the database which handled the
same tables, you need to use LOCK/UNLOCK tables.
MySQL daemon don't lock tables or records if you don't require this.
Can I ask if this is in fact accurate? As I understand it, MySQL does a
fairl
RE COMPANY
Permanent e-mail address : [EMAIL PROTECTED]
[EMAIL PROTECTED]
- Original Message -
From: "Jeff Snoxell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 12, 2002 6:57 PM
Subject: More locking issues
&
Hi,
I'm new to MySQL. I see you all talking about locking databases etc... but
isn't that the point of having a database server? So you don't have to
worry about record locks?
I'm designing the backend for a popular site where a user's visit will
result in multiple read/write operations on a d
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
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:
mysql> LOCK TABLES users read;
Query OK, 0 rows affected (0.00 sec)
mysql> select * from Logger limit 1;
ERROR 110
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
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:
mysql> LOCK TABLES users read;
Query OK, 0 rows affected (0.00 sec)
mysql> select * from Logger limit 1;
ERROR 110
> 2.
> The following is the extract from mysql documentation:
> "
> In MySQL Version 3.23.7 and above, you can insert rows
> into MyISAM tables at the same time other threads are
> reading from the table. Note that currently this only
> works if there are no holes after deleted rows in the
> table
Hi,
1.
Does mysql inherently implement locking implicitly?
2.
The following is the extract from mysql documentation:
"
In MySQL Version 3.23.7 and above, you can insert rows
into MyISAM tables at the same time other threads are
reading from the table. Note that currently this only
works if there a
20 matches
Mail list logo
