You could also use collections to separate the articles. That will allow you to keep the URI's the same but keep the articles logically separated. In the long run I think you will find that putting them in separate databases will be more trouble than it's worth.
----
Clark D. Richey, Jr.
Principal Technologist, Federal
Mark Logic Corporation
1600 Tysons Blvd
Suite 835
McLean, VA 22102
Phone: 240 - CLARK - 07
(240 - 25275 - 07)
[email protected]
www.marklogic.com
This e-mail and any accompanying attachments are confidential. The information
is intended solely for the use of the individual to whom it is addressed. Any
review, disclosure, copying, distribution, or use of this e-mail communication
by others is strictly prohibited. If you are not the intended recipient, please
notify us immediately by returning this message to the sender and delete all
copies. Thank you for your cooperation.
On Oct 11, 2010, at 2:02 PM, helen chen wrote:
> We have a system that needs to deal with articles going through staging stage
> and production stage. Basically when article comes in, it stays in staging
> stage. After a lot of operations and verifications the article gets
> published, then at this time it will be moved to production stage. The
> article's content can be changed during staging stage and can also be
> changed when moving to production stage.
>
> I'm thinking of two ways to do it:
> 1. One way is to put the data into separate directories within the same
> database, like staging articles will be under /staging directory, production
> articles will be under /prod directory. Using this way I only need to manage
> one database, and maybe in the future if I need to search data cross stage,
> it is doable. But inside code I have to constantly check if I'm in staging
> stage or production stage so that my search or article's uri will be build
> correctly.
>
> 2. Another way is to use different database for each stage. Using this way
> the article's uri can be the same, a lot of code can be the same because they
> will work in separate database, as long as database is pointing correct, the
> code will return correct dataset. But if in the future we ever want to do a
> search cross stage, it is going to be a problem.
>
> Does anyone has any suggestions on this?
>
> Thanks in advance for your help,
>
> Helen
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
