Hi!

Just a note, there will be a MySQL Meetup on the 6th at the Elysian Brewery here in Seattle. Meeting time is 7 PM.

Address is:
Elysian Brewing Co.
1221 E Pike St


Yes, I will be in town and attending the meeting :)

Seems like things are heating up in the IT job market here in the Northeast. In the last 30 days, I know of several people that have left stable, secure positions for more lucrative jobs. On the other hand, a Fortune 500 company in the area announced several IT development layoffs of which I personally knew two people who got "downsized".

The Computing Technology Industry Association recently conducted a survey that pointed out 60% of IT workers are looking for new jobs. Of those 60%, a staggering 81% of those job seekers consider their job searches "active".

Wow, nearly 50% of IT workers are actively searching for another job. I used to think thinks like perks and training were the key to keeping employees happy. I have found out that those things are nice, but they don't keep a …

So, I have what I consider a feature request for binlog. I’d like there to be an option to log DDL only or DML only, or both DDL and DML (current functionality).

Sure, I can take a diff of the schema, or grep for TABLE or INDEX and put that into its own logfile; however, this is something that really should be an option to mysqlbinlog.

(http://bugs.mysql.com/bug.php?id=16916)

Check this out. Someone has built and AJAX powered version of mytop, the little console based MySQL monitoring tool I wrote years ago. I guess it's now buzzword compliant.

If you can't wait to get your hands on it, head over to the AjaxMyTop project on SourceForge.

Everything old is new again. :-)

(comments)

I never realized it until now, but there is no specific forum category for migration from PostgreSQL to MySQL at http://forums.mysql.com/ (only one for Other Migration).

Unfortunately, there might still be more people who migrate from MySQL to PostgreSQL than the other way around, but it should be one of MySQL's big goals to change that - and I believe that this is a realistic goal. The lack of a specific forum category has the potential to make people believe that this is meant to be too unrealistic - so I think, there should be one.

I also recently filed a feature request for MySQL MigrationToolkit to add functionality for migration from PostgreSQL to MySQL (http://bugs.mysql.com/bug.php?id=16508). I know that it's no easy task to provide good migration functionality - but there's probably …

This week IBM became the latest proprietary database vendor to add a free offering to their lineup, according to ZDNet:

DB Express-C is the same database as IBM’s commercial offerings but the company places limits on what kind of hardware it can run on.

It can be deployed on systems with two processor cores or up to two dual-core chips on Advanced Micro Devices- or Intel-based servers. The memory limit is 4GB but there are no limits on the size of database or number of users.

IBM’s decision to add a free database to its lineup follows moves by its largest rivals in the database business, Oracle and Microsoft.

…

The three corporate-database providers are all seeking to appeal to software developers, who help influence companies’ technology decisions. In addition, open-source databases, which generally include …

Ok, on with triggers, I'll start migrating the existing triggers then I'll look at triggers as a workaround for computed columns.
Firebird syntax for SAVE_SALARY_CHANGE trigger (active AFTER UPDATE) on table EMPLOYEE is:

...
BEGIN IF (old.salary <> new.salary) THEN
INSERT INTO salary_history
(emp_no, change_date, updater_id, old_salary, percent_change)
VALUES (
old.emp_no,
'NOW',
user,
old.salary,
(new.salary - old.salary) * 100 / old.salary);
END

Now in MySQL terms it becomes:

CREATE TRIGGER save_salary_change AFTER UPDATE ON employee
FOR EACH ROW BEGIN
IF (old.salary <> new.salary) THEN

INSERT INTO salary_history
(emp_no, change_date, updater_id, old_salary, percent_change)
VALUES ( old.emp_no,
now(),
user(),
old.salary,
(new.salary - …

More on calculated columns, here is the create table statement for one of Firebird's Employee.fdb database:

CREATE TABLE SALARY_HISTORY (
EMP_NO EMPNO NOT NULL,
CHANGE_DATE DATE DEFAULT 'NOW' NOT NULL,
UPDATER_ID VARCHAR(20) NOT NULL,
OLD_SALARY SALARY NOT NULL,
PERCENT_CHANGE DOUBLE PRECISION DEFAULT 0 NOT NULL
CHECK (PERCENT_CHANGE BETWEEN -50 AND 50),

NEW_SALARY COMPUTED BY
(OLD_SALARY + OLD_SALARY * PERCENT_CHANGE / 100),

PRIMARY KEY (EMP_NO, CHANGE_DATE, UPDATER_ID),
FOREIGN KEY (EMP_NO) REFERENCES EMPLOYEE (EMP_NO));

I'd go for a trigger based implementation.

After this I'll look at implementing checks and foreign keys (color coding to highlight relevant code samples, I know it can be ugly ;-))

Hi, I've decided to make an in depth test of MySQL's new functionalities by porting Firebird's EMPLOYEE.FDB database to MySQL 5.1.5, here is what I found, I hope it will be useful for people porting apps from MySQL to Firebird and vice-versa.
First of all, a screenshot (taken from Firebird's excellent Flamerobin admin tool) showing the actual employee.fdb structure.
Note the presence of generators, (aka sequences) won't be available in MySQL, I'll mimic them with autoincrement fields.
Also, look at triggers, two of them ("set_cust_no" and "set_emp_no") are used to implement an autoincrement-like key in tables, again there is no need to even try to reimplement them in MySQL.
Also, at first I won't try to implement domains, exceptions and calculated columns as I'm not aware of a clean implementation for them in …

Joy of Tech is one of the great online cartoons of the web.  Though it's focused primarily on the Mac world, there's often some good Linux and Windows humor like this one, also available as a poster:

• Joy of Tech: Latest cartoon
• Joy of Tech: …