Page 1 of 1
What skills are similar to InnoDB
Posted: Thu Dec 18, 2008 8:48 am
by Preciseresourcing
I am a recruiter looking for a developer with InnoDB skills and other advanced MySQL skills, however, these seem to be rare?
If someone doesn't have InnoDB, what skills are similar or easily transferable?
Re: What skills are similar to InnoDB
Posted: Thu Dec 18, 2008 9:33 am
by Eran
Do you know what InnoDB is..?
Re: What skills are similar to InnoDB
Posted: Thu Dec 18, 2008 9:44 am
by mintedjo
pytrin wrote:Do you know what InnoDB is..?
*Waves hand*
I do i do!
Re: What skills are similar to InnoDB
Posted: Thu Dec 18, 2008 9:46 am
by onion2k
InnoDB is not a skill. It's a database engine. The skill required to do things with InnoDB would be database admin and/or SQL programming.
Re: What skills are similar to InnoDB
Posted: Thu Dec 18, 2008 9:55 am
by Preciseresourcing
Are there any other "similar" transactional engines that people who haven't worked on InnoDB, would easily be able to pick up?
Many Thanks
onion2k wrote:InnoDB is not a skill. It's a database engine. The skill required to do things with InnoDB would be database admin and/or SQL programming.
Re: What skills are similar to InnoDB
Posted: Thu Dec 18, 2008 10:31 am
by Eran
MySQL has two transactional storage engines - InnoDB and BerkelyDB. You can read more on the different storage engines in the manual -
http://dev.mysql.com/doc/refman/5.0/en/ ... gines.html
Being familiar with a particular storage engine is less important than being familiar with the concept of transactions itself. If data integrity is important to you, you should look for people who know how to use transactions. Better research a little on what the terms mean when you post looking for technical help, so you won't get burned.
Re: What skills are similar to InnoDB
Posted: Sun Dec 21, 2008 9:53 pm
by volomike
Most guys who do PHP that I know -- they do MySQL. A few know PostgreSQL and SQLite as well. And of those whom know MySQL, most know that MySQL comes with a few transaction engines inside that you can choose from, but the only ones I've used were InnoDB and MyISAM. They both have their pluses and minuses depending on the task. When you create a table in the database in MySQL, you choose whether to use MyISAM or InnoDB or another transaction engine. A given MySQL database can mix InnoDB and MyISAM tables, as well.
Most MySQL guys I know are already up to speed on InnoDB and MyISAM. If I were to take a survey, I'd say that's about the norm for 2/3rds of all MySQL devs out there.
So, for me, if a guy has used PHP for a year, more than likely he knows MySQL, and more than likely he knows to use InnoDB or MyISAM inside MySQL, and which works better for the given task.
Now, if you ask a candidate who knows PHP and ask what's InnoDB and they don't know, then heck yeah -- that's a red flag that they're a very junior PHP programmer.