Arjen wrote:

> 
> It's a standard feature, not enabling it cripples the functionality.
>

Then, and I'm not trying to be flip here, it should be built in, not an
add-on module.
 
> The reality that I see on a daily basis is that
>  a) people are not so familiar with Gentoo procedures as you may wish;
>  b) complete noobs use Gentoo too.
> 
> As to why (b) happens I do not know, you can take pride in the fact that the
> Gentoo name is spreading to these quarters too... but since this is indeed the
> case, you do need to take it into consideration, as well!
> 
> Anyway, the result of the above is a lot of trouble, confusion and questions.
> While I'm all for choice, I also like to be pragmatic and would suggest that 
> in
> this case, giving you as expert the choice of switching it off makes more 
> sense
> than requiring other less experienced users to switch it on.
>

So let me tell you how I got bit by this - yes, we started down a path that
needed innodb, and didn't have the flag set, thus got the error.  I had to
read the appropriate MySQL docs (MySql Ref. Maunal), then wonder why it wasn't
working on Gentoo.  Hitting ufed, I found the flag, set it and re-compiled.

But the fun doesn't end there.  Setting up innodb's conf file is poorly 
documented
and confusing.  Unless one finds just the right html page with the help.  Then
when it's set up, it sucks up a huge amount of resources - if you never plaaned
for it and add it, you could be in a disk space crunch.

InnoDB not being default on Gentoo is the least of the problems.   Thus,
I go back to the suggestion - if it's that important, build it in.  Otherwise,
please save all of use the additional - poorly documented, need to properly
set up innoDB when we don't need it.  

When it gets built-in, fine a - noinnodb USE flag would be of use.
 
> 
> Another reason is this. Unfortunately, some people still claim that MySQL
> doesn't support transactions and such, even though it has for many years.
> I am quite tired of having to keep explaining this, it's silly and should not 
> be
> necessary.

I understand that.  Really, and I do let people know that it does.

> We're all here to promote open source, and not to make life more difficult for
> eachother, or to stick with decisions that cause others more work (i.e. 
> keeping
> them from doing other more useful work). That's what I strive for.
> Please give way just a little bit, for everybody's benefit. It won't hurt you.

But people need to read some documentation and try to develop problem solving 
skills.
And if they need to not think in detail about admining their system, they really
should be looking at a Linux with some gui sysadmin tools and probably a binary
only distribution.  (I'm not trying to be eliteist on this.)

FWIW - I went to www.mysql.com during this and the only place that innodb is
mentioned, is in the forums.  In that forum, there is no sticky concerning
installing it or what it does.

While Gentoo has some issues - innodb, dbx, mysql, USE flasg are pretty 
scattered,
it seems some minor changes over at MySQL.com would go a long way towards
clarifying things - like an easy to find FAQ - does MySql support transaction
processing?  Yes, with innoDB.  And - To configure innoDB,   Please refer to 
Ch 15 of the Reference manual, which can be found - <URL>.

Also, I notice there are sections in the manual on installing on Linux.  While
there is no information other than on RPM installation.  Even in the comment
section.  Wouldn't it be easy enough to add the steps to install on Gentoo
with a suggestion to set the innodb USE flag should transaction processing
be required - along with other useful USE flags as appropriate - dbx, to the
comment section?

Bob
-  

--
gentoo-user@gentoo.org mailing list

Reply via email to