Re: [cowiki-dev] Releasing coWiki with the "working" parser

Hakan Kuecuekyilmaz wrote:

> Quoting Paul Hanchett <[email protected]>:
>
>> My responses are inline!
>>
>> Daniel T. Gorski wrote:
>>
>>> On 11 Jul 07:44, Paul Hanchett wrote:
>>
>
>> You mean "not" bother me, right?  The problem is that InnoDB is not
>> standard in the hosting community.  MyISAM may not be reliable enough to
>> put the corporate jewels into, but it's plenty good enough for 90% of
>> the net.
>
>
> Which hosting community do you mean? I don't know _any_ ISP, which 
> uses XAMPP
> for their systems. They compile their stuff on their own: Apache, 
> MySQL, and
> PHP. One of the biggest ISP in Germany "United Internet" even have 5 to 7
> kernel hackers for doing their own Linux kernel stuff. Go figure.

XAMPP isn't the issue-- It's just a convenient tool (especially in 
Win32) to get all the stuff up and running easily.  Not all ISP's (or 
distro's) are running with InnoDB, and you can't find that out just by 
seeing if they support MySQL. 

>
>
>>>> I know the effort was to get database reliability because of the 
>>>> "Magic"
>>>> problem, but it has been demonstrated with the new code so I am as 
>>>> ready
>>>> to roll back the database as you are the parser.
>>>>
>
> AFAIK, the BEGIN and ROLLBACK stuff should be ignored by a MyISAM only 
> MySQL
> server. I don't know about the DDL statements with "Engine InnoDB". Can
> somebody try this on a MyISAM only mysqld? It should work, but I am 
> not 100%
> sure :)
>
> If the DDL is accepted by a MyISAM only MySQL server there would be no 
> need to
> "roll back" to MyISAM, as it should be compatible on DDL and DML level.

Apparently Daniel is checking to see if the database supports InnoDB, 
and if it doesn't the install fails and you can't get any further.  :-(  
I guess I need to come back to troubleshooting this some more...