Issue Type: Improvement Created: 2010-10-25T13:01:35.000+0000 Last Updated: 2013-03-13T20:55:22.000+0000 Status: Open Fix version(s): - Next Mini Release ()
Reporter: Nathan Bell (nathanpbell) Assignee: Marc Hodgins (mjh_ca) Tags: - Zend_Queue
Related issues: Attachments: - ZF-10597-test-setup.txt
In order to use table names other than 'queue' and 'message' in Zend_Queue_Adapter_Db, one must currently extend three classes:
It seems like this is something that should and could be supported easily through an option key or setter method.
Posted by Marc Hodgins (mjh_ca) on 2010-11-25T08:43:40.000+0000
Patch with unit test and updated docs attached.
Also attaching instructions on TestConfiguration.php settings and related steps to turn on the the Zend_Queue_Db unit tests to make it easier for whoever is testing/applying this patch. Thanks!
Posted by paulo vitor bettini de albuquerque lima (paulovitorbal) on 2011-06-30T13:14:36.000+0000
As well as the name of the table, we should have an option to the schema too. It will be nice, while working with postgres.
Posted by paulo vitor bettini de albuquerque lima (paulovitorbal) on 2011-06-30T13:35:33.000+0000
While working with the Db adapter, why not use the Zend_Db_Table classes, for message and queue? Doing this, we could intercept the methods used by, like the insert, or the update.Instead of using the database adapter methods for update, select, insert, I purpose to use the Zend_Db_Table methods.
Have you found an issue?
See the Overview section for more details.