Re: migrating user accounts

2002-06-18 Thread Joshua Horton

Thanks for the response!  I'm comfortable with it but I wanted a second
opinion.

-Josh

Galen Wright-Watson wrote:

 On Wed, 12 Jun 2002, Joshua Horton wrote:

  Hi,
 
 snip
  First, I'm having trouble determining whether or not it is possible
  to drop a user, or whether I have to go in and delete all that user's
  records in the grant tables.  I revoke ALL PRIVILEGES from the user, but
  his entry still apears in the mysql.users table.  I have heard it is
  undesirable to directly manipulate the users table.
 snip

 I think you can only remove a row from MySQL.user directly.  True, GRANT is
 preferred to add and alter user accounts, but DELETEing the user's entry in
 MySQL.user is fine.

 -
 Before posting, please check:
http://www.mysql.com/manual.php   (the manual)
http://lists.mysql.com/   (the list archive)

 To request this thread, e-mail [EMAIL PROTECTED]
 To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED]
 Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: setting up two instances of mySQL

2002-06-13 Thread Joshua Horton

Hi, I don't want to get in the way, but I am experiencing similar issues.  Here's the
problem I'm trying to find a resolution to:

We have one instance of MySQL (it was configured and installed once).  This instance 
has
one 'test' 'database', and one 'mysql' 'database'.  The mysql database contains the 
grant
tables.

I want to create a few other 'databases'.  One should be used for keeping recipies, for
instance, and the other will contain the data I use for the electronic key card system 
I
use in my house (for instance).  Both databases run under the same 'instance'.

The recipe database is updated frequently, because I am active in a cook's collective 
and
we routinely update each other's recipies as we develop more refined ways of making the
dishes.  The key card database is not updated frequently, but is heavily accessed by
several custom-made hardware devices.

One day, a bug in the network protocol I use to connect the card swipe device to the
database causes some of the data in the database to become corrupted in the key card
database.  This happens as I get home late at night after bar hopping, and I don't
discover it until noon.  The corruption involves data that was deleted, so I need to
restore that database to just before midnight, using the full backup I wisely took at 
8PM
before going out to the bars, in conjunction with the update log which I have on a 
RAID5
device for protection.

The problem is, that if I restore the database from the last cold backup, then apply 
the
update log until midnight, I will lose all transactions that occurred against the 
recipe
database between midnight and noon the next day!

Oracle and SQL Server allow you to restore databases independently of one another.  I
cannot discern the method to do so in MySQL.  Surely this is a common requirement?  Is
there an easy answer I have overlooked during my evaluation of the restore options?

By the way, the above scenario assumes MyISAM table types.  I understand from other
postings that InnoDB can restrict the options even further.  The obvious solution seems
to be separate MySQL 'instances' for each database you want, so that the transaction 
logs
are kept distinct from one another.  If this is the preferred solution, I would be
interested to hear how some production environments have been set up.

Thanks!
Josh Horton

Francisco Reinaldo wrote:

 Hi Chris,

 I am Tom, you know your manager, did you say that I am
 wrong!!!

 Just kidding :-).

 Well I cannot find any good reason for having two
 databases in two different instance. Do you have two
 Oracles or Microsoft SQL Server instances in the
 computer? Nope.

 The only reason when that is acceptable, is when you
 want to keep two version of the same database engine.
 Like having 3.23 and 4.0.

 Having two MySQL instances is going to complicate
 things making everything more difficult to maintain
 and install.

 Good Luck.
 --- Cal Evans [EMAIL PROTECTED] wrote:
  The pros are you can run them under separate
  user/group ids therefore you
  can make it much harder for someone with access to
  only one to get to the
  other's data.
 
  The cons are that you will have 2 copies running
  therefore it will take
  longer to maintain.
 
  =C=
 
  *
  * Cal Evans
  * Journeyman Programmer
  * Techno-Mage
  * http://www.calevans.com
  *
 
 
  -Original Message-
  From: Chris Stefanick
  [mailto:[EMAIL PROTECTED]]
  Sent: Wednesday, June 05, 2002 7:56 AM
  To: MySQL Support
  Subject: setting up two instances of mySQL
 
 
  I have one product already using a mySQL database.
  We just inherited a new
  product (via an acquisition) that uses it's own
  mySQL database which we're
  going to stick on the same server.  My manager wants
  me to setup a second
  instance of mySQL on the machine for the new
  product's database.  I don't
  see the point.  Why not just have both databases
  running under the same
  instance of mySQL?  Which brings me to my question.
  What are the pros and
  cons of setting up multiple instances of mySQL on
  the same machine?
 
  Thanks so much,
  CS
 
 
 
 -
  Before posting, please check:
 http://www.mysql.com/manual.php   (the manual)
 http://lists.mysql.com/   (the list
  archive)
 
  To request this thread, e-mail
  [EMAIL PROTECTED]
  To unsubscribe, e-mail
  [EMAIL PROTECTED]
  Trouble unsubscribing? Try:
  http://lists.mysql.com/php/unsubscribe.php
 
 
 
 
 -
  Before posting, please check:
 http://www.mysql.com/manual.php   (the manual)
 http://lists.mysql.com/   (the list
  archive)
 
  To request this thread, e-mail
  [EMAIL PROTECTED]
  To unsubscribe, e-mail
  [EMAIL PROTECTED]
  Trouble unsubscribing? Try:
  http://lists.mysql.com/php/unsubscribe.php
 

 __
 Do You Yahoo!?
 Yahoo! - Official partner of 2002 FIFA 

migrating user accounts

2002-06-12 Thread Joshua Horton

Hi,

I have been watching the list for a while now as I get to know
MySQL.  I must admit that it is one of the more vibrant communities I
have encountered.   I have seen many good answers and even better
questions, but I haven't seen my particular issues come up. I have two
questions, one specific and one general.
First, I'm having trouble determining whether or not it is possible
to drop a user, or whether I have to go in and delete all that user's
records in the grant tables.  I revoke ALL PRIVILEGES from the user, but
his entry still apears in the mysql.users table.  I have heard it is
undesirable to directly manipulate the users table.
Second, I need to migrate a MyISAM MySQL server from one machine to
another, where the target MySQL server is set up using InnoDB as the
default table type.   I am planning to use the mysqldump files to
recreate the databases on the InnoDB machine.  My question is, what is
the best method to get the users and grants to transfer to the new
machine?  I have heard that I should disable the default table type (set
it to MyISAM), make a mysqldump of the host 'mysql' database, grep
through the dump file and globally replace the old hostname with the new
hostname, and then use that file to recreate the 'mysql' database on the
target machine.  Does this sound reasonable?  What, if anything, will
this do to the InnoDB catalog?  I would like to avoid manually
recreating each user if possible.

I suppose my best bet is just to try it out, but I wanted to get a more
seasoned opinion, if possible.

Thanks a million!

Joshua Horton


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php