On Tuesday, September 4, 2018 at 4:14:24 AM UTC-7, Jun Omae wrote:
>
> On Tue, Sep 4, 2018 at 12:29 PM RjOllos wrote:
> >
> >
> >
> > On Tuesday, September 4, 2018 at 3:24:36 AM UTC, RjOllos wrote:
> >>
> >> I don't see a way to set a persistent default storage engine for each
>
On Tue, Sep 4, 2018 at 12:29 PM RjOllos wrote:
>
>
>
> On Tuesday, September 4, 2018 at 3:24:36 AM UTC, RjOllos wrote:
>>
>> I don't see a way to set a persistent default storage engine for each
>> database/schema. However, rather than requiring the MySQL instance default
>> storage engine to
On Tuesday, September 4, 2018 at 3:24:36 AM UTC, RjOllos wrote:
>
> I don't see a way to set a persistent default storage engine for each
> database/schema. However, rather than requiring the MySQL instance default
> storage engine to be set (in the system-wide my.cnf configuration), we
>
On Mon, Sep 3, 2018 at 7:31 PM Mingxing Tian wrote:
> RjOllos於 2018年9月4日星期二 UTC+8上午10時00分41秒寫道：
>
>>
>> On Monday, September 3, 2018 at 6:58:08 PM UTC-7, Mingxing Tian wrote:
>>>
>>> I confirm that the engine is already InnoDB, but it still detects errors.
>>>
>>> [image: 0001.png]
>>>
RjOllos於 2018年9月4日星期二 UTC+8上午10時00分41秒寫道：
>
> On Monday, September 3, 2018 at 6:58:08 PM UTC-7, Mingxing Tian wrote:
>>
>> I confirm that the engine is already InnoDB, but it still detects errors.
>>
>> [image: 0001.png]
>> C:\Users\Administrator>trac-admin "D:\myproject" deploy
>>
On Monday, September 3, 2018 at 6:58:08 PM UTC-7, Mingxing Tian wrote:
>
> I confirm that the engine is already InnoDB, but it still detects errors.
>
> [image: 0001.png]
> C:\Users\Administrator>trac-admin "D:\myproject" deploy
> "D:\myproject_deploy"
> Error: The current storage engine is
