I would like to see Zend_Db_Table to query everything with the table name. I want a find($my_id) result in a: "SELECT `table_name`.* FROM `table_name` WHERE `table_name`.`primary_key_id` = '$my_id'"

Is there a reason not to incorporate the table name into the default queries? This allows for flexibility in future joins where there might be a second table with the same column name as the primary_key_id in the main table.

Zend_Db_Table already allows you to make joins.

How to print the mysql error ? If direct php , we can use mysql_error(). But i dont know how to find here.?? plz reply as soon as possible

You need to enable error reporting in your bootstrap file. This can be done with the following code:

I know Zend_Db_Table allows you to make joins but in the Zend_Db_Table::find() and Zend_Db_Table_Row::_getWhereQuery() function it would be good to have the primarys with the table name so that you don't an error when you have two tables with the same key.

Example: If table_2 has id as primary key then this will cause an error

The methods to create your queries are more convenience functions and to give you a standard interface so that changes in syntax per DB Brand can be normalized and make your app more portable, if you wanted to say, switch from MySQL to Oracle.

However, since no DB is going to let you get away with amigious column names, such as what you described, the onnus is on the developer to pass the table name with the column name when getting into situations where the field could be ambigious, which with the ZF is going to be through the fetch* style, and not find. Find is only for single table look ups by primary key... in other words not for joined tables and other complex queries.

Yeah, I get that... but why not add the table name into the query? What's the catch? Why not?

Sometimes you create an app and u want to make it slightly more complex and a join can add valuable data in a rather seemless way. This would enable that functionality in a fast and easy way that's very cost-effective.

Thanks. I have done that already. But what i want is, how to display MYSQL ERRORS.? While getting error, ZF send the page to Its error.phtml page and calles the Error controller automatically. So, i could not able to find the mysql error and to debug it.

-- Mugesh

@mgordon

Well, if you need to move from find to fetchAll, the amount of refactoring would be kind of low, since you would already have to modify it a bit to do the join anyway.

@mugesh

Which errors are you looking for? Connection issues can be caught and displayed with a try/catch block around that code (we do it in our bootstrap).

As for other DB errors, if you catch the right Exception object (Zend_DB_Exception, etc) you should be able to get the right error. Zend_Exception should be your last (default) catch block, so that general/other errors can be caught at that point.

HTH,
-e