Regarding this issue, I have found that by rebooting the computer,
these problems have gone away (for now). I have a feeling that
this was a subtle permission/ownership problem. Some of the
databases were installed by direct file copy. although this method
has worked well for me on slackware and re
On Tuesday 30 October 2007, Warren Young wrote:
> Tim Johnson wrote:
> >> It isn't "broken," per se.
> >
> > When you say that it isn't "broken", could you please elaborate?
>
> Once again: It seems to me that you're seeing a purposeful choice of
> configuration. It could very well be that the c
Tim Johnson wrote:
It isn't "broken," per se.
When you say that it isn't "broken", could you please elaborate?
Once again: It seems to me that you're seeing a purposeful choice of
configuration. It could very well be that the configuration makes sense
in some one's use. The fact that i
ct: Re: Can't find file: './mysql/(database_name).frm'
Tim Johnson wrote:
>
> Is there a possible repair routine to run?
It isn't "broken," per se.
Someone chose to build it with this configuration, and presumably that
person made a choice that is sensible for thei
On Tuesday 30 October 2007, Warren Young wrote:
> Tim Johnson wrote:
> > Is there a possible repair routine to run?
>
> It isn't "broken," per se.
When you say that it isn't "broken", could you please elaborate?
And thanks in advance, because, from where I'm sitting, time is money
and I
Tim Johnson wrote:
Is there a possible repair routine to run?
It isn't "broken," per se.
Someone chose to build it with this configuration, and presumably that
person made a choice that is sensible for their needs. If it doesn't
work for you, you can either build MySQL from source with the
On Tuesday 30 October 2007, Warren Young wrote:
> Tim Johnson wrote:
> > The file pattern is *not* as I expressed it above.
>
> Yeah, I figured that out, and ignored the error in my reply.
>
> The answer remains the same: unless you're purposefully doing something
> weird, there's a configuration e
Tim Johnson wrote:
The file pattern is *not* as I expressed it above.
Yeah, I figured that out, and ignored the error in my reply.
The answer remains the same: unless you're purposefully doing something
weird, there's a configuration error in that MySQL build. It's not that
the configurati
On Tuesday 30 October 2007, Warren Young wrote:
> Tim Johnson wrote:
> > Can't find file: './mysql/(database_name).frm' for numerous databases.
>
> That's the file the actual table data is stored in. Unless you're on a
> shared machine and are trying to
Tim Johnson wrote:
Can't find file: './mysql/(database_name).frm' for numerous databases.
That's the file the actual table data is stored in. Unless you're on a
shared machine and are trying to run a private copy of MySQL, you
probably don't mean to put stor
using Distrib 5.0.45 on ubuntu 7.04, mysql was installed via adept manager.
I'm getting many error messages on the type:
Can't find file: './mysql/(database_name).frm' for numerous databases.
The mysql database was installed automatically during installation, and
I'm
11 matches
Mail list logo
