teek > abhinandan.prat...@shapeblue.com>>
>> Date: Tuesday, 30 August 2016 at 4:23 PM
>> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
>> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
>> Cc: Rajani
; Date: Tuesday, 30 August 2016 at 5:25 PM
> To: Abhinandan Prateek abhinandan.prat...@shapeblue.com>>, "dev@cloudstack.apache.org dev@cloudstack.apache.org>" dev@cloudstack.apache.org>>
> Cc: Rajani Karuturi mailto:raj...@apache.org>>, Raja
> Pullela mailto:r
i mailto:raj...@apache.org>>, Raja Pullela
mailto:raja.pull...@accelerite.com>>
Subject: Re: Few tables in cloudstack schema use MyISAM engine
I cannot think of any. Most probably in all cases the engine was not explicitly
specified and the default got used. As per below default was myi
August 2016 at 4:23 PM
To: "dev@cloudstack.apache.org"
Cc: Rajani Karuturi , Raja Pullela
, Koushik Das
Subject: Few tables in cloudstack schema use MyISAM engine
Hi,
Was there any specific reason that some tables in cloudstack schema use
MyISAM engine.
I know of “ quota_accou
Hi,
Was there any specific reason that some tables in cloudstack schema use
MyISAM engine.
I know of “ quota_account” that I created and put in the diff table type
unknowingly. I assume such is the case with other such tables –
load_balancer_cert_map, monitoring_services, nic_ip_alias, sslce
