Hi All,
I am needing to access a sub databases through main database.
I have one main database and serveral sub databases. For accessing those
databases I am using mysql prepared statements, But the performance I am
getting because of this is very low.
Can anyone suggest me any alternate way
Manasi Save schrieb:
Hi All,
I am needing to access a sub databases through main database.
I have one main database and serveral sub databases. For accessing those
databases I am using mysql prepared statements, But the performance I am
getting because of this is very low.
Can anyone
RENAME TABLE
olddb.table1 TO newdb.table1,
olddb.table2 TO newdb.table2
put the whole list in here, the whole statement will be applied to the
system atomically
The database has 1200+ tables, so your approach seems like more work to
me. As it is, all I'm doing is:
service mysql stop
mv
Does this work if any of the tables are InnoDB?
On Mon, Nov 23, 2009 at 8:17 AM, Robinson, Eric eric.robin...@psmnv.comwrote:
RENAME TABLE
olddb.table1 TO newdb.table1,
olddb.table2 TO newdb.table2
put the whole list in here, the whole statement will be applied to the
system
You don't even need to stop the server afaik. As mentioned previously,
though, works for MyISAM only.
On Mon, Nov 23, 2009 at 3:17 PM, Robinson, Eric eric.robin...@psmnv.comwrote:
RENAME TABLE
olddb.table1 TO newdb.table1,
olddb.table2 TO newdb.table2
put the whole list in here, the
The Spider Storage Engine
http://forge.mysql.com/wiki/The_Spider_Storage_Engine
This Thursday (November 26th, 14:00 UTC), Giuseppe Maxia will present
the Spider Storage Engine. This session was originally scheduled for
October 15th but had to be postponed for technical reasons.
Here's from the
Hello list :)
I am developing an application that will show records in paginated
documents, i.e. 10 records per page
Lets supose this row structure
MyTable
ID(autoincrement) SectionID Name Description
The ID is automatic autoincrement for unique records, the SectionID is to
separate
On Mon, Nov 23, 2009 at 7:37 AM, Johan De Meersman vegiv...@tuxera.bewrote:
You don't even need to stop the server afaik. As mentioned previously,
though, works for MyISAM only.
While this is strictly true there are some big caveats (flushing tables,
etc). It is safer to shut down the
Hello list :)
I am developing an application that will show records in paginated
documents, i.e. 10 records per page
Lets supose this row structure
MyTable
ID(autoincrement) SectionID Name Description
The ID is automatic autoincrement for unique records, the SectionID is to
separate
The order the records are returned is not guaranteed unless you
specify an ORDER BY. You could run the same query multiple times and
the order the records are returned could be different each time.
Although this is rarely the case, especially with caching enabled.
Always do an ORDER BY with
On Nov 22, 2009, at 8:54 AM, Ryan Chan wrote:
Hello,
Is it common heard from people that if you have large table (assume
MyISAM in my case), you need large memory in order to have the
key/index in memory for performance, otherwise, table scan on disk is
slow.
But how to estimate how much
So, as a followup, I ran mysqldump on the actual server (with the output
directed over AFP to another machine on the network) -- as opposed to running
mysqldump on the destination server and connecting to the databases over TCP/IP
(both are running 5.1.39 PPC 64-bit). *That* dump file imported
Hi,
I've installed MySQL 5.1.41 x86_64 on fresh install of Mac OS X Server 10.6.2
(where the bundled version is 5.0.82. Just a couple questions:
1. Have any of your encountered compatibility issues with MySQL 5.1.x on Mac OS
X Server 10.6.2? (Since I am in the process of migrating several
13 matches
Mail list logo
