phpMinAdmin is a powerful minimalist MySQL editor

5 More Discussions You Might Find Interesting

1. What is on Your Mind?

Boy, is the shell powerful.

Reading replies to questions, as an amateur, I have learnt a lot from you pros on here. The shell in any of its guises is serioulsy poweful. With so many transient and resident commands at one's disposal is there anything, non-GUI, that cannot be done inside a default shell and terminal? ...

2. Shell Programming and Scripting

An curious idea, how to make it by the powerful script?

I use a simple script to do some quantum calculations with gaussian package. the script as follows #!/bin/sh #put a gaussian input file into a new folder in the same name #and submit this new job for i in *.gjf do FN=$( echo $i | sed 's/.gjf//') mkdir $FN mv...

3. Shell Programming and Scripting

set EDITOR=vi -> default editor not setting for cron tab

Hi All, I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by set EDITOR=vi it does not open a vi editor , rather it do as below..... ///////////////////////////////////////////////////// $ set...

4. Shell Programming and Scripting

Any way to make scp more powerful?

Hello, I'm writing a script to automate the delivery of our code to different target environments and I was wondering if there's any way to cut down on the number of authentications that are needed. The script has to deliver to three different boxes (two directories on two boxes and one...

5. OS X (Apple)

Is Mac OS X Server Really Powerful?

Look We all know that Linux is almost BulletProof and about 40% faster than Win2K3 Server, When running Oracle DB, Right? Now my Question is can OS X run just as Well as Linux as a Server being PowerPC and Whatever, Can it be just as stable? Now You Tell me, Which is most Practical: Linux...

LEARN ABOUT SUSE

apache::session::lock::mysql

Session::Lock::MySQL(3) 				User Contributed Perl Documentation				   Session::Lock::MySQL(3)

NAME

       Apache::Session::Lock::MySQL - Provides mutual exclusion using MySQL

SYNOPSIS

	use Apache::Session::Lock::MySQL;

	my $locker = Apache::Session::Lock::MySQL->new();

	$locker->acquire_read_lock($ref);
	$locker->acquire_write_lock($ref);
	$locker->release_read_lock($ref);
	$locker->release_write_lock($ref);
	$locker->release_all_locks($ref);

DESCRIPTION

       Apache::Session::Lock::MySQL fulfills the locking interface of Apache::Session.	Mutual exclusion is achieved through the use of MySQL's
       GET_LOCK and RELEASE_LOCK functions.  MySQL does not support the notion of read and write locks, so this module only supports exclusive
       locks.  When you request a shared read lock, it is instead promoted to an exclusive write lock.

CONFIGURATION

       The module must know how to connect to your MySQL database to acquire locks.  You must provide a datasource name, a user name, and a
       password.  These options are passed in the usual Apache::Session style, and are very similar to the options for
       Apache::Session::Store::MySQL.  Example:

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockDataSource => 'dbi:mysql:database',
	    LockUserName   => 'database_user',
	    LockPassword   => 'K00l'
	};

       Instead, you may pass in an already opened DBI handle to your database.

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockHandle => $dbh
	};

AUTHOR

       This module was written by Jeffrey William Baker <jwbaker@acm.org>.

SEE ALSO

       Apache::Session

perl v5.12.1							    2008-01-08						   Session::Lock::MySQL(3)

UNIX and Linux RSS News