IdeaJam(tm) : Prevent Design running against database

Domino Designer / : Prevent Design running against database

Tue, 22 Apr 2008 19:02:43 +0000

Author: Peter Presnell
Tags: Design refresh
Idea:

I would like to have the ability to mark a database so that its design is not refreshed automatically by the Design task running on the server. When set I can only update the design via a manual refresh/replace.

This would be very useful in situations in which a database has a significant number of individual design elements that are inherited from various other templates residing on the same server. Whilst I can remove all the template references it is neither an easy or reliable task to put them back at a later stage (when I do want to get the latest design changes from those other templates). The scenario I often encounter is the development work is done on an application but somebody is working on separate development impacting one or more of the templates I am using. Between Unit Testing/QA starting and deployment to production I really do not want any of these template changes to be applied to my application automatically.

re: Prevent Design running against database

Tue, 22 Apr 2008 20:32:24 +0000

Author: Michael Kinder
Comment: Really, more of a question then a comment. Do you mark template inheritance references in the database, or in a template that the database inherits from?

Mike Kinder

re: Prevent Design running against database

Wed, 23 Apr 2008 05:47:08 +0000

Author: Rob Goudvis
Comment: The scenario you described can be avoided by having separate templates. One for development and another one for Unit Testing and one for production. When you give these templates a different name you will minimise the work to move a template to another phase of your project.

I think this way of working is less dangerous than allowing the refresh to be blocked.

re: Prevent Design running against database

Wed, 23 Apr 2008 08:37:22 +0000

Author: Paul Davies
Comment: @2 - this is how I work - it is very effective. Each template has it's own filename, template name and db title - the template name and db title are always the same to recduce confusion