|
The user profile initial library list only works if you have a separate job for each business logic connection. The initial library list is less useful when you use a single job that swaps profiles.For library list, you can obviously change the library list on everyrequest.
It's a little on the expensive side, but I haven't run any benchmarksin a while.
If you only have a single environment, you may also be able to ignoreit,
but I find that situation to be rare; I've usually got at least one other environment for testing.
Agreed, one environment is rare. However, the environment (Library list)
defaults to the default library list for the user, so if you setup your
users correctly you can almost ignore that issue. If you have a "test"
user and a "production" user then the test user's library list is test,
and the production user's library list is production, all you need to do
is change your connection string. And since that should be a config
setting anyway... simple. :-)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.