As others have pointed out, if you are referring to "MySQL Cluster"
proper, aka NDB, the default table type on your 'client' nodes is
irrelevant. NDB data is stored on the data nodes using the NDB
storage engine. If you have a cluster-construct based on 'normal'
MySQL tables, that is another matter entirely.
If you do need to switch table types, there is no need to
export/reimport. simply:
ALTER TABLE mytable Engine = MyISAM;
It may be time consuming depending on the amount of data you have stored.
- michael dykman
On Sun, Apr 29, 2012 at 2:06 PM, Brown, Charles <CBrown@stripped> wrote:
> Well said. Thanks so much.
>
> Sent from my iPhone
>
> On Apr 29, 2012, at 8:02 AM, "Reindl Harald" <h.reindl@stripped> wrote:
>
>>
>>
>> Am 29.04.2012 14:50, schrieb Brown:
>>> is a complain I received from one of my developer that after following our
> MySQL
>>> Cluster migration, tables are now defaulting to innodb (how can he tell)
>>
>> as already said:
>>
>> the builtin default has changed an you have to configure MyISAM
>> as default yourself with "default-storage-engine = myisam"
>>
>> and yes, InnoDB can be a big problem if your application is only
>> tested against MyISAM because it works completly different inside
>>
>>
> ********************************************
> This message is intended only for the use of the Addressee and
> may contain information that is PRIVILEGED and CONFIDENTIAL.
>
> If you are not the intended recipient, you are hereby notified
> that any dissemination of this communication is strictly prohibited.
>
> If you have received this communication in error, please erase
> all copies of the message and its attachments and notify us
> immediately.
>
> Thank you.
> ********************************************
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql
>
--
- michael dykman
- mdykman@stripped
May the Source be with you.
