You can easily say it's actually two application there for two databases its fine. For example let say the staging have no access from the web only from the company intra net while the public application should be browsed from the employs home. In that case the design looks fine.
About the undo thing. You can't use "auto increment" with that approach, I think. Also the IO is much more then it should be. But, I guess you don't have more 10 users in the staging application and there for no performance issues. It looks like a newbie work around but if its working just the way you like and it doesn't drag you to do more work around, this is what work around usually do, then way change it. BUT, a make over is a great time to try to think about the whole challenge from a new perspective. Until you will think your database is not "fairly complex" don't rest. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" 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
