Getting Into Encoding

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
Ekki
Posts: 34
Joined: Sun 24 Nov 2013 18:50
Location: Ilmenau, Germany
Contact:

Getting Into Encoding

Post by Ekki » Wed 03 Sep 2014 13:36

Hi,

can anyone please point me to some entry points (Documents, etc.) concerning encoding?

Have to 'sync' PostgreSQL (UTF-8), DevArt LinqConnect and DevExpress Web Forms...

Currently I'm facing artefacts on DX side and exceptions on DA side as soon umlauts are used...

Any documents etc, are highly appreciated.

BR,

Ekki

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: Getting Into Encoding

Post by MariiaI » Thu 04 Sep 2014 13:53

Please try the following:
- set the Unicode connection string parameter value to True
or
- set the Charset connection string parameter value to Utf8

To do it in Entity Developer, open Database Explorer, right-click the Database Connection and select Edit Connection Properties from the shortcut menu, and click the Advanced button. Set Unicode to True (or 'Character set' to the necessary value) in the opened dialog box and save changes.

For more information please refer to:
1) http://www.devart.com/dotconnect/postgr ... arset.html
2) http://www.devart.com/dotconnect/postgr ... arset.html

Please tell us about the results.

Ekki
Posts: 34
Joined: Sun 24 Nov 2013 18:50
Location: Ilmenau, Germany
Contact:

Re: Getting Into Encoding

Post by Ekki » Fri 05 Sep 2014 11:51

Hi Mariia!

I did as you wrote (did set Unicode to True) and have now full roundtrips from UI to DB (Admin) via Linq and back. Thanks a lot.

There's one question remaining: As my application uses English as UI language (the data language may differ) I would prefer to force your modules to print the exception messages in EN (currently they show up in DE). Is there any way to achieve this directly by configuring your components at run-time? If not, what you suggest?

Thx ia again,

Ekki

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: Getting Into Encoding

Post by MariiaI » Mon 08 Sep 2014 13:25

As my application uses English as UI language (the data language may differ) I would prefer to force your modules to print the exception messages in EN (currently they show up in DE). Is there any way to achieve this directly by configuring your components at run-time? If not, what you suggest?
No, there is no way.
All LinqConnect exceptions are given in English. The exceptions, which you are getting, are from the server-side and, thus, the language of the error messages are determined by the server settings.

Post Reply