Andrew McMillan <and...@morphoss.com> writes:
>> Hi,
>>
>> I found a workaround/solution:
>>
>> postgres stores some information at install time about the locale:
>>
>> postgresql.conf:lc_messages = 'en_US.UTF-8' # locale for
>> sys
>> postgresql.conf:lc_monetary = 'en_US.UTF-8' # locale for
>> mon
>> postgresql.conf:lc_numeric = 'en_US.UTF-8' # locale for
>> num
>> postgresql.conf:lc_time = 'en_US.UTF-8' # locale for
>> tim
>>
>> previously that was set to de_DE which is apparently not working in
>> combination with davical.
>
> DAViCal creates the database with a UTF-8 encoding and PostgreSQL does
> not allow UTF-8 encodings to be created if the database was originally
> initialised with an incompatible encoding such as ISO-8859-15 etc.
>
> There's not really any way around this. I don't believe that the
> PostgreSQL folk will fix the issue - there are excellent performance
> reasons behind their decision. CalDAV specifies UTF-8 as the One True
> Encoding and so naturally DAViCal wants to store in a database that is
> capable of that.
>
> Possibly I could add a check during the installation, but it would say
> little more than the PostgreSQL error message did, and it would most
> likely say it in English, which would be a poor option indeed.
>
> Regards,
> Andrew.
Hi Andrew,
thank you very much for your detailed explanation!
>From a normal user prespective I would very much welcome a check and an
explanation or hint for a workaround from the davical side. And english
is very much acceptable. However the same error message in english would
not help at all and not because of the english part.
I would need a level of detail like:
grep UTF-8 postgresql.conf or die "ERROR: davical needs UTF-8, but your
postgresql.conf does not allow this. Please consider changing the lc_*
settings in postgresql.conf"
to get me any further.
Let me explain from my no-database-guru point of view.
* I have never used postgresql and I installed it especially for
davical. I do not maintain SQL servers for many users, instead
I want to sync my telephone calendar with my desktop.
* I did not configure postgresql for the locale de_DE as far as I
remember. This is against my intention. I have explicitly set my
root account and /etc/default/locale to LANG=C in order to get
english error messages for system things, which helps for
retrieving solutions in google a lot.
* Most gnome session are using de_DE as my children like their
openoffice menu in german
* the de_DE 'leaked' somehow to postgresql, probably because of the
way synaptic or the "gnome root terminal" or sudo behave when
getting root. As you have explained there is an additional
performance impact connected to this setting. So quite strange that
this is propagated automatically here. On the other hand reportbug
thinks my gnome-session is using
Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
This snippet comes from my original bug report, so I cannot give
any real source for the de_DE value in postgresql.conf
This:
> DAViCal creates the database with a UTF-8 encoding and PostgreSQL does
> not allow UTF-8 encodings to be created if the database was originally
> initialised with an incompatible encoding such as ISO-8859-15 etc.
Did never happen in my opinion. If I understand it correctly, I had
zero databases while de_DE was in the postgresql.conf.
* The postgresql error message of postgresql confused me, because the
strings LC_CTYPE and LATIN1 are nowhere in any of the involved
commands or configuration files. You need a lot of know-how to
parse this error message and come to the explanation you gave
above. Or employ try and error like I did later.
I am somehow aware that this is not related to davical at all, but more
to me being confronted to a complex SQL thing. :)
What do you think of adding a sentence/instruction to the
installation document, which allows the user to check his
postgresql.conf for UTF-8 support? Like the "grep UTF-8 postgresql.conf"
pseudo code above?
kind regards
Frank
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
