upgradefrom20050530to20050616.sql contains COLLATE too

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
8/22/2005 9:12:21 AM
Gravatar
Total Posts 25

upgradefrom20050530to20050616.sql contains COLLATE too

and is there any reason to have some SQL scripts in UNICODE?
8/22/2005 1:35:36 PM
Gravatar
Total Posts 18439

Re: upgradefrom20050530to20050616.sql contains COLLATE too

Thanks I'll remove that. btw, if you are doing a clean install you don't need the upgrade scripts, that is only for previous installations.

All the SQL scripts should be in UNICODE shouldn't they? Isn't that the culture neutral way to go?
8/23/2005 2:31:14 AM
Gravatar
Total Posts 25

Re: upgradefrom20050530to20050616.sql contains COLLATE too

ok, only for someone upgrading, of course...

scripts in unicode - I only dont know if these are needed, if code is in pure 7bit ascii (if it is - if not, then it is simply interresting where nonascii is needed)

anything related to localization interrests me, I have read article and web about mono string collation rewrite from ICU, there may be many issues too if it will not be absolutelly compatible with windows, even with bugs and nonstandards leaved ...

 

8/23/2005 2:22:33 PM
Gravatar
Total Posts 18439

Re: upgradefrom20050530to20050616.sql contains COLLATE too

When you generate SQL script files from MS SQL 2000 Enterprise Manager, unicode is the default and the other options are MS DOS and Windows ANSI.

I think unicode would be best because maybe some cultures want to use special characters for table and column names
You must sign in to post in the forums. This thread is closed to new posts.