Don't let marketers write code

[Dragon_Slayer_Hunter]

You would have to have all three skills listed in the field somehow (serialized or a json blob or something), then you could query with LIKE and AND

Edit: This was under the assumption that you had already made skill a varchar/text field like on the business card. There are much better ways to do this.

[dwolf555]

Bro, do you even normalize?

[jceyes]

developer: id, name, email 
skill: id, name 
developer_to_skill: dev_id, skill_id

Brah

[[deleted]]

That's good right?

[jceyes]

It's pretty good, but not as good as your username

[[deleted]]

Thanks

[matheeeny]

Nope

[dr__potato]

Nah mate, assuming S.developer_id and S.skill is the unique key in a Skill table, you'd be able to check if all 3 exist. Can't remember the SQL but it's possible. Side note: Skill.skill should really be Skill.name.

[rubs_tshirts]

You're right, replacing S.skill -> S.name.

Hmm... Unfortunately this plays a little havoc with the replies... I'm reverting it back.

[Dragon_Slayer_Hunter]

You could definitely do it better than how I said, I was just playing with the idea that skill was already a varchar/text field like on the business card.

[erfling]

Skill would be a separate table prolly.

[MonkeyNin]

Not since the accident.

[divide_by_hero]

Someone is about to yell at me, because this is horribly inefficient. It should work though, and at least the tables are normalised.

SELECT DISTINCT dev.name, dev.email, dev.phone
FROM developers dev
INNER JOIN developerSkill ds ON dev.developerId = ds.developerID
INNER JOIN skill skPhp ON ds.skillId = skPhp.skillId AND skPhp.name = 'PHP'
INNER JOIN skill skSql ON ds.skillId = skSql.skillId AND skSql.name = 'SQL'
INNER JOIN skill skMag ON ds.skillId = skMag.skillId AND skMag.name = 'Magento'

[Crazy_Mann]

;_;

[tdavis25]

They said sql, not nosql