Hi Igor,

Those debug asserts are meant to help developers find and fix mistakes in the code. For example if the sql parameter names or types or counts declared in code don't match the parameters in the actual stored procedure.

If you are encountering such errors in mojoPortal code please let me know where they are so I can fix them, ie post a stack trace. I would not expect you to be encountering lots of errors such as this but if you are encountering them I would like to get bug reports about the specific details.

When not in debug mode sql server is fairly forgiving and errors won't happen in production if the types and counts are correct and only the names are wrong, but still its best to track down any such mistakes and fix them.

Best,

Joe

Hi Igor,

That is an error in custom code not in mojoPortal code. So the debug assert is alerting you to the mistake in the custom code. In your custom code DBSearch.FetchSearchKeywords there are parameters declared incorrectly for the store procedure it calls. If you compare the params in the stored proc and fix the params in the code so they match the proc this debug assert error will stop happening. 

If we did not have the debug assert it would be harder to find this error in your custom code and it could result in a bug that is hard to find. But since you get this error during debugging it brings your attention to the problem so you can fix it.

Best,

Joe

varchar is limited to 8-bit representation. nvarchar can store Unicode data, so they are not the same data type.

http://stackoverflow.com/questions/144283/what-is-the-difference-between-varchar-and-nvarchar

Hope that helps,

Jamie