The PHP Town Hall podcast, with hosts Amanda Folson and Ben Edmunds, has released its latest episode: Episode #53 - Developer Relations, Travel, and Bedbugs with Jessica Rose . Jessica is the lead of developer relations at Crate.io, the company that created the CrateDB product.

Jessica talks about some of her own experiences in developer relations along with some of Amanda's own experiences doing the same in past roles. They also talk about the strain developer relations can put on other parts of peoples' lives and different perspectives on work. They also talk about programming bootcamps, online training, hammocks and speaking at conferences.

You can catch this latest episode either using the in-page audio or video player or you can download the audio and listen offline. If you enjoy the show you can subscribe to their feed to get the latest episodes as they're released.

That Podcast, hosted by PHP community members Beau Simensen and Dave Marshall, has posted their latest episode - Episode #39: Public Relations

Beau and Dave discuss skiing, skateboarding, Rebekah's book launch, Bullet Journaling, Rachel Nabor's Practical Cartooning for Technical Folk, Beau getting back into DJing, Dave dabbling in Bitcoin bot trading, Logan, and multiuser SaaS.

Other topics mentioned include this article on what it feels like to be an Open Source maintainer and some thoughts about multi-user logins from Jonty Behr. You can listen to this latest episode either using the in-page audio player or by downloading it directly. If you enjoy the show, be sure to subscribe to their feed and follow them on Twitter for updates when new shows are released.

New from the ZendCasts.com site there's a new screencast looking at the relations you can create between Doctrine and your Zend Framework applications.

This short podcast covers how you can easily build a form using Zend’s MVC model via Zend_Controller and using Doctrine for persistence. You can download the source code or browse it online. Enjoy!

This screencast is part of a series they've been doing on Doctrine including Doctrine Relations and Data Fixtures and Writing Doctrine Unit Tests with Zend_Test.

Jani Hartikainen talks about some updates he's made to the ModelForm class for the Zend Framework and how its been reworked a bit to take advantage of Zend_Db_Table.

I've been reworking the ModelForm class for ZF a bit. Earlier this year, I discussed porting it to use Zend_Db_Table with Matthew Weier O'Phinney, for using it with Zend Framework. I initially had done some checking on Zend_Db_Table, and some small code changes to modify the class to use it instead of Doctrine, but I ran into some issues. Now, I've had some time to think about it, I've reworked the class slightly and added basic Zend_Db_Table support, too...

He talks about the two sides - the issues that came up (including relation support and differences between Zend_Db_Table and Doctrine) and how they were overcome (creating an adapter setup to accommodate for the relations issues).

The International PHP Magazine has posted the results from their latest poll where they asked their readers "which is the most common PHP database problem?"

The options were:

• Using MySQL directly
• Not using auto-increment functionality
• Using multiple databases
• Not using relations
• The n+1 pattern

And coming out on top (with 27.5%) was "Not using relations" in the SQL statements made. Following close behind was "Using MySQL directly" and falling in last was "Not using auto-increment functionality".

Be sure to vote in this week's poll that asks "Which is Truest?" - given several popular opinions on PHP, pick the one that you think is the most true.

The International PHP Magazine has posted the results from their latest poll where they asked their readers "which is the most common PHP database problem?"

The options were:

• Using MySQL directly
• Not using auto-increment functionality
• Using multiple databases
• Not using relations
• The n+1 pattern

And coming out on top (with 27.5%) was "Not using relations" in the SQL statements made. Following close behind was "Using MySQL directly" and falling in last was "Not using auto-increment functionality".

Be sure to vote in this week's poll that asks "Which is Truest?" - given several popular opinions on PHP, pick the one that you think is the most true.

It seems like there's not a site out there anymore that doesn't use a database of some sort. Frankly, they're just a simple way to get the storage you need without the hassle of having to manage the resource yourself. It even comes with its own language to help query the data! Of course, with the good comes the bad, and this new article from IBM's developerWorks site about five common database mistakes.

If only there were one way to use databases correctly... You can create database design, database access, and the PHP business logic code that sits on top of it in any number of ways, and you often end up getting it wrong. This article illustrates five common problems in database design, in the PHP code that accesses databases, and how to fix these problems when you see them.

The problems they discuss are:

• Using MySQL directly
• Not using auto-increment functionality
• Using multiple databases
• Not using relations
• The n+1 pattern

Each of the items is discussed and explained with code samples for both the good and the bad side to make comparison easier. Knowing these issues before you develop your system definitely makes it easier, but they're still useful as a tool to fix things as well.

It seems like there's not a site out there anymore that doesn't use a database of some sort. Frankly, they're just a simple way to get the storage you need without the hassle of having to manage the resource yourself. It even comes with its own language to help query the data! Of course, with the good comes the bad, and this new article from IBM's developerWorks site about five common database mistakes.

If only there were one way to use databases correctly... You can create database design, database access, and the PHP business logic code that sits on top of it in any number of ways, and you often end up getting it wrong. This article illustrates five common problems in database design, in the PHP code that accesses databases, and how to fix these problems when you see them.

The problems they discuss are:

• Using MySQL directly
• Not using auto-increment functionality
• Using multiple databases
• Not using relations
• The n+1 pattern

Each of the items is discussed and explained with code samples for both the good and the bad side to make comparison easier. Knowing these issues before you develop your system definitely makes it easier, but they're still useful as a tool to fix things as well.