Let's say that you want to set up a one-to-many relationship between two tables: Artists and Albums because you've refactored my ZF1 tutorial. [...] Assuming you're using Zend_Db_Table, the easiest way is to turn off the integrity check and do a join in a mapper or table method.

He includes a few lines of source to illustrate, calling the "setIntegrityCheck" value to "false" to tell ZF not to worry about the additional join value over to the artists table. The result is a new column value with the artist's name instead of just the ID.

If you use Doctrine, then you probably know how lazy loading can hurt your performance. I carefully craft every query to everything that I need in one shot, but only what I need. One thing that evaded me at first was the i18n part. I am pleased with the way Doctrine + symfony magically creates all my models and database tables with i18n support.

She talks a bit about the internationalization (i18n) support is put into the schema.yml file and the bit of confusion she had over how to handle a left join using its structure. The key lies in the Translation relationships.

In the last few weeks, I've talked with a number of friends about career changes. Some are feeling antsy and just want to move, others are starting their own consulting, and others are starting and joining startups. While I've done all the above - to varying levels of failure success - I thought I'd share the things I've learned along the way.

He gives six things to keep an eye out for when considering your entry into the startup world:

• Everyone does everything
• There's no career path
• You never have enough money
• v1.0 never looks like the original Vision
• Every founder believes in him/herself
• Most startups don't explode, they fizzle

He's not saying all of this to push you away from startups, though - more to help you go in "with eyes open" and ready to ask the harder questions before you get into a bad situation.

If there are relations (an Author has a Book, for example). the generated forms will complain that the generated Models need a __toString() method to be used in the Form/View. In grails, this is the case, but every domain (corresponding to a Symfony 'model') has an implicit toString() method already generated, which return the string ":". For most production work, you'll want to override it with whatever you need the string to read, but for prototyping, it's fine.

He went in and modified the Symfony core to add in a __toString call that would return the object correctly. Several of the commentors agree with his frustration and some of the Symfony developers even chime in with some of the reasoning behind why it's like that.

The goal of the PHP Evangelism Team is to bring together the right people, resources and experience from across the PHP Community to provide developers with the process guidance and best practices needed to create new opportunities for the web.

They're also looking to help support local user groups and aid in any PHP-related event they can. You can subscribe to their mailing list to get more information as the group develops. Check out the post for the address to join the list.

Ever wished for an easy way to transform SQL result sets into XML? It's a PEAR package named XML_Query2XML, and it provides a comprehensive framework to efficiently turn the results of a database query into a customizable XML document. This article introduces the package, and demonstrates useful real-world applications, including using it with XSL and XPath, combining it with data from external Web services, and creating database dump files.

They go through the installation and the steps to create the XML:

• Convert SQL to XML
• Transform XML output with XSL
• Customize XML output
• Work with SQL joins
• Filter SQL records with XPath
• Merge data from multiple sources
• Create database backups

Check out the full tutorial for an excellent guide to using this powerful PEAR package.

I'm currently working on a CAPTCHA plugin for DokuWiki and thought about providing audio output for users not able to see the image. This is pretty simple for CAPTCHAs - there is no need for complicated speech synthesis because you only need recordings of the 26 possible letters. But you need a way of joining those recordings on the fly...

There was an example he found previously, but it seemed like overkill, so he rolled together his own solution - a 24 line script that takes in the filenames of the wav files and spits back out the joined resource. This functionality has already been added to the CAPTCHA plugin if you'd like to check it out.