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

On 13 Jul 10:41, Paul Hanchett wrote:

> Daniel T. Gorski wrote:

> >>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.  :-(  

> >Using a non-transactional persistence engine like MyISAM with coWiki (or
> >better any software) is negligent, thats all.

> >The installer process fails (or better: stops with a qualified message) to
> >avoid any "wrong security feeling" for the user.
> >
> >We decided to support MySQL >= 4.0 which supports InnoDB without problems
> >and I don't really see where the problems are now. Maybe it would be better
> >to concentrate on other important issues. This one is solved IMO.

> 4.0 does not universally support InnoDB Daniel.  Nor does 4.1.  The 
> InnoDB engine has to be explicitly turned on and it may not be in all 
> hosting situations.  I am really quite disappointed in this. 

> I am also not satisfied with the analysis of where the coWiki "Magic" 
> issue comes from.  The "magic" itself is not a /database /issue, it 
> looks more like program logic.

Yes, probably. But starting to trace this bug without the transactions build
in, would leave an "uncertainness factor". I still can not understand, why
you try to resist using transactions. Ok, just leave it if you want. Put
"mysql://" instead of "mysql+innodb://" in the core.conf RESOURCE entries.
It will still work. But as said many timess before, the data loss will come
sooner or later, __especially__ if you want to have more complex operations
on the data base in the future.

You may also disable the filesystem file locking in FileOutputStream if you
like.

It's tedious. If you want, I can change the installer, so that it does not
stop if InnoDB is not available with a big red blinking message: "Your data
is not even safe on your local machine, do not use with concurrent users! We
guarantee the integrity of the database until your first HTTP-request your
fresh installed coWiki page. From then on you are responsible yourself if
your data messes up - coWiki is one-use, one-way throwaway article. Thank
you".

Is this that what you want?

regards dtg