I'm not familiar with Postgres or schemas, but I think a prefix is suitable. The table name does not need to affect the MVC names - just set var $useTable = 'whatever_long_table_name' in your model.
On Nov 30, 6:33 am, BravoFoxtrot <[EMAIL PROTECTED]> wrote: > What are the best practices for organizing tables? > > My scenario is that I want to have a number of common tables and then > create a number of modules (plugins) that share the common tables. I > would like to keep the plugin tables organized in some way. > > For example I have the following common tables: > users > groups > login_history > > I have the following plugin tables: > quizzes > questions > answers > questions_users (HABTM) > > I want to be able to organize questions and answers. I could do this > using a prefix like quiz_questions. The problem with this method is > that it makes for long ugly table/controller/model names especially > for HATBM relationships. And I don't think the bake scripts in 1.2 > handle the relationships properly. > > I'm using postgres so I thought schemas would be a better way to go. > There is a patch herehttps://trac.cakephp.org/ticket/1623to allow > for multiple schemas and it seems to work. The problem is this may > restrict what databases I can run on and all it does is add the schema > to a search path. If two or more schemas contain the same tablename, > I'm not sure this implementation works. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
