Interview with Masood Mortazavi, MySQL Engineering Manager at Sun


 
Thread Tools Search this Thread
Top Forums Web Development MySQL DevZone RSS Interview with Masood Mortazavi, MySQL Engineering Manager at Sun
# 1  
Old 12-17-2008
Interview with Masood Mortazavi, MySQL Engineering Manager at Sun

Masood Mortazavi is an Engineering Manager at the Sun Database Group. After the acquisition of MySQL, and along with the rest of Sun's original database technology group, he joined the MySQL organization to form the larger Sun Database Group. In this interview, Masood talks with Lenz about the flexibility and diversity of Sun as a workplace, his life prior to joining Sun and his current assignment to improve the MySQL code contribution process.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. What is on Your Mind?

Junior engineer attending a senior engineering interview.

So the company I work for is interviewing for a senior engineer, DevOps position. I was requested to participate in the last interview. I realize, among many things, personality and group cohesiveness are a contributing factor when considering a new employee. With this in mind I only asked... (4 Replies)
Discussion started by: Circuits
4 Replies
Login or Register to Ask a Question
Apache::Session::Lock::MySQL(3pm)			User Contributed Perl Documentation			 Apache::Session::Lock::MySQL(3pm)

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.10.1 2010-10-18 Apache::Session::Lock::MySQL(3pm)