b) I have 200 tables. I don't want to have to recreate indexes for
every table if I have to restore. I'd rather spend an hour restoring
from tape and let replication catch me up.
Why would you have to recreate the indexes? The dump will contain this
information in the CREATE statements.
An easier (and more secure) way, surely, is to use one-way encryption... and
if a user forgets his/her password, replace it with a random alphanumeric
string and mail that to them instead with instructions to change it to one
of their own choosing as soon as possible.
Mike
- Original
- Original Message -
From: Benjamin Pflugmann [EMAIL PROTECTED]
To: Mike Hall [EMAIL PROTECTED]
Cc: Michael Collins [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Sunday, August 11, 2002 7:05 PM
Subject: Re: [OT] assigning new passwords (was: Need reversible encryption
as string)
On Sun
What are you trying to do here?
MySQL is giving this error because the table 'test' does not exist in the
'test' database. Are you mistaking database for tables? I think perhaps you
need to take a look more carefully at the manual about creating tables.
Mike
- Original Message -
From:
Replication, however, is no good for scaling update load. What happens when
you're update load is too much for the box? Are you just meant to buy a
bigger box? What happens if you already have the biggest box and the update
load is too high? Is there no way to scale the update load wide in MySQL?
I had this problem.
For some reason MySQL has decided to look at your tmp directory (which
contains vi.recover) instead of your data directory. Compiling
with -DHAVE_BROKEN_REALPATH fixed it for me, on FreeBSD 4.6, linuxthreads
and dual CPU.
--Mike
- Original Message -
From: Dicky
Either that, or buy a commercial MySQL License
- Original Message -
From: Oliver Six [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; MySQL [EMAIL PROTECTED]
Sent: Monday, July 08, 2002 12:03 PM
Subject: Re:Re: Licensing--web site is schizophrenic
Hi,
does this mean that whenever I write a
Take a dump
- Original Message -
From: Todd Cary [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 08, 2002 1:38 PM
Subject: Moving a DB from one Server to another
Is there a quick and simple way to move a MySQL DB from one server to
another
MySQL server? Can I just copy
Okay:
FreeBSD 4.5-STABLE with LinuxThreads 2.2.3. and MySQL 3.23.51. Duel PIII
1Ghz with 1G of RAM. All from source.
Compiled okay and came through super-smack and crash-me tests okay. But a
few hours later, for no reason, MySQL decided to look at /var/tmp instead of
/usr/local/mysql/var for
Corrupt index, hmm? I'll check that in a moment - thanks.
Probably a sensible idea to limit the query too - I think I'll order by date
desc too just to make sure that recent mail gets sent.
Cheers
--Mike
- Original Message -
From: Benjamin Pflugmann [EMAIL PROTECTED]
To: Mike Hall
I think you better show us the script. This might help to figure out the
problem.
Okay, here it is:
-- Start
#!/usr/local/bin/php -q
?php
// Include library files
include 'config.php';
include 'feedlib.php';
// Init log
$log = new ParserLog;
// Define location of mailer lock file
$lock =
Okay, I am having some trouble with MySQL that could *potentially* be quite
serious. A little background first.
I'm running PHP 4.2.0 (Release) and MySQL 3.23.49a over five servers. One
server is a MySQL Master with PHP CGI version, two are MySQL slaves and the
other two are Apache webservers
Is there any chance at all that a field name is appearing in your
WHERE clause? For example:
UPDATE foo SET flag = 0 WHERE foo_id = foo_id;
foo_id = foo_id of course matches all.
No, the query is hard coded to WHERE Sent = 0.
Not much room for that kind of error in this example, but
13 matches
Mail list logo
