Since virtualization has been removed, I was wondering if you are going to remove SettingsID from everything as well? It would make sense to, as it was only there for virtualization and now has no function.
WGB EnterprisesopenSourceC.org
Bill,
The @SettingsID value touches a fairly large surface area of our code (as you well know). We opted to not do it for Community Server 2008, but will do it in a point release afterwards. There is more to it of course than just removing it (index analysis, query plan analysis, etc) so we wanted to do this in steps.
Thanks,David L. Penton
Treat it as depreciated. We will be removing it from the tables, likely in the next release (service pack/point release) of Community Server. We want to do it in such a way that is easy for client of all size databases.
Thanks,David
That's cool. I guess my biggest question is, do we need to support/use it when CS2008 is released? Or, will it just be hanging there unused and not required? Or will it be a combination of the two? Just curious for the controls that I need to rebuild once the SDK is released.
Cool, one less thing to worry about.
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com