Hi Jelle,

I'm about to make a little release today but will try and fix this for the next release after this if you can help me figure out a good solution that won't break in other situations like upgrades where dbo was already used during object creation.

It might work if all the scripts where changed to not use any prefix at all. Can you help me with testing on a local machine? If you have time it would be much appreciated and would help get a solution for this.

What I'd like you to do is test this theory with a clean install using scripts with all owner prefixes removed starting with script Setup/applications/mojoportal-core/SchemaInstallScripts/mssql/2.3.4.config

and then the scripts newer than that in the SchemaUpgradeScripts/mssql folder

So you'd have to remove the prefixes using find and replace and maybe review visually some to make sure.

If that works then send me the modified scripts and I will test if it also works when upgrading installations that used dbo before. If so then we will replace with these new scripts and going forward always leave out owner prefix and this won't be a problem anymore and won't need any complicated instructions for this situation.

I think it should work but we need to make sure with testing.

Thanks,

Joe

I think the easiest thing is if I just go through the upgrade scripts and replace dbo. with [dbo]. and then make sure I always use [dbo]. going forward.

Sorry it took me so long to grok this issue.

Thanks,

Joe

Hi Jelle,

My policy for svn commit access is basically that it is only needed for those who are consistently working on and contributing to the project. Those without svn commit access can contribute by sending patch files which I will review and commit if I agree with the changes or provide feedback if I thnk changes are needed. If over time I find you are consistently providing patches that require no modifications based on my review or making substantial contributions in feature development then I will happily grant you commit access.  Of those that do get commit access, hopefully some will show interest in assisting with review of patches from others and gradually we will build a team of core committers. I know you have been in the mojoPortal community for quite a while and I have no doubt that you will do good work. Its just a getting to know you phase with patches in the beginning to establish a working relationship that builds confidence and trust.

For adding new files its easier if you zip them and send separate from the rest of the patch. Also I often have trouble applying patches to resource files (.resx) so as long as you do svn update to make sure your copy is up to date, its easier for me to just replace the file so sending separate from the patch file is preferred.

Best Regards,

Joe