Post reply

Globilization in SQL Server

  • June 22, 2005 at 3:47 pm

    #93397

    Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/dasanka/globilizationinsqlserver.asp




    My Blog: http://dineshasanka.spaces.live.com/

  • July 4, 2005 at 6:00 am

    #570621

    Hello. Sorry about bad english. We are a Brazilian Sotware Producer and we develope a program that runs in Brazilian Portuguese, German, English, French, Italian, Spanish, and Turkish for a german customer using MSDE and we had too many problems with regional options and language. At end of development we choose for to delive the database language files and attach them on customer´s sql server machines to prevent data errors. But, how to perform when a customer tries to insert a string that uses simple quote mark, like: " Copo D´Água " ? The product can be running in various MSDE different languages. We will don´t know which of them. My regards. Reginaldo.

  • July 4, 2005 at 6:54 am

    #570635

    what are the data types that are using

    use nvarchar , nchar and ntext




    My Blog: http://dineshasanka.spaces.live.com/

  • July 5, 2005 at 9:15 am

    #570892

    There is an error in Bulgarian months - for april - needs to be corrected - well, I do not have a cirilic right now and I cannot write it down but it's wrong...

    Hope this will help.

  • July 6, 2005 at 12:13 am

    #571102

    Sorry for the mistake. thankx for the information




    My Blog: http://dineshasanka.spaces.live.com/

  • July 6, 2005 at 1:52 pm

    #571485

    Globalization is misspelled.

  • July 6, 2005 at 10:04 pm

    #571633

    Major mistake!!!

    will be corrected




    My Blog: http://dineshasanka.spaces.live.com/

  • July 10, 2005 at 6:40 am

    #572725

    Corrections are done. Title caption needed to be corrected.




    My Blog: http://dineshasanka.spaces.live.com/

  • July 4, 2006 at 4:45 am

    #647347

    To avoid single quoted problems make sure to validate the input. Use of single quotes is a well know SQL inject attack used from hackers. Try replace each single quotes for two single quotes.

    I´m also a brazilian developer and the SQL server date handle provide most os bad time. First if the SQL is installed at us language setting the session language is ineffective. This is a bug of SQL server.

    My personal experience proved reset default server language, set dateformat, set session language and set user language sometimes dont works!

    In addiction for the problems the use of diferent collations at the same database can destroy the simpliest comparation "a" = "a" can be evaluate to false!

    Consider the cenario where u send updates for the customer to create a new table. The SQL server at the customer have a different default collation. Expect for a lot of problems.

    And at end the britanic imperial system default for all US softs is weird.

     

    Jean

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply