Paul Jones has a post to his site looking at SQL schema naming conventions and some of his own thoughts on the matter. There's a lot of different camps of thought around naming, much less database ones, and he makes a few suggestions learned from his experience over time.

Several weeks ago I asked on Twitter for SQL schema naming conventions from DBA professionals. (I’m always interested in the generally-accepted practices of related professions; when I can, I try to make my work as compatible with theirs as possible.)

I got back only a handful of responses, representing MySQL, PostgreSQL, and DB2 administrators, really not enough for a statistically useful sample. Even so, I’m going to present their anonymized responses here, because they led me to work I had not previously considered at length.

He asked about things like singular vs plural names, primary key choices and naming of association tables. The uses the rest of the post sharing the responses he got from his questions with a good range of responses representing both sides of each question. He wraps up the post looking at what these answers mean to the average developer and the answers that Joe Celko and Simon Holywell have to say on the matter.

In this new entry on the APress "Inside Open Source" blog, Matt Wade shares some of his thoughts on one of the more popular PHP frameworks - the Zend Framework.

I've found that using the framework has significantly decreased my development time and really just given me cleaner, easier to maintain code. Of course, these are the goals of any framework. I do have a couple of issues I've come across and it is those I'd like to talk about.

The two issues he mentions were problems with the Zend_Db component (not everyone has just one primary key in their table) and caching problems with Zend_Cache (no unique lifetimes included).

In this new entry on the APress "Inside Open Source" blog, Matt Wade shares some of his thoughts on one of the more popular PHP frameworks - the Zend Framework.

I've found that using the framework has significantly decreased my development time and really just given me cleaner, easier to maintain code. Of course, these are the goals of any framework. I do have a couple of issues I've come across and it is those I'd like to talk about.

The two issues he mentions were problems with the Zend_Db component (not everyone has just one primary key in their table) and caching problems with Zend_Cache (no unique lifetimes included).