|
I don't know of a specific limit, but if you're using profile documents on the Domino server, the number of profiles is probably not the cause of your problem. Profile documents are cached in memory the first time they are used, and the Domino server has multiple processes handling your URL requests. Each process has its own version of the cache, and if the profile document was modified recently, they may not all agree. So it's a matter of chance whether you get an answer from a process whose cache is up to date.
If you need changes you make to show up right away in your app, use a conventional document or view so you can @DbLookup or @DbColumn. This may not perform as well, but you can use NoCache to force it to be up to date. In web apps, profiles are best for values that change infrequently. Do you have comments on this Ask the Expert question and response? Let us know.
|
