Re: [SL] What client encoding goes with what chart of accounts?

[Bob G. <bo...@rc...>]

On Wed, 2007-05-23 at 08:49 -0500, Bob Gustafson wrote:
> This is probably a dumb question, but here I am an english
> speaker/writer trying to create a german language database.
>=20
> This error occurred after attempting to create the sql-ledger database
> with the Germany-DATEV-SKR03 chart of accounts.
>=20
> No multibyte encoding was selected.
>=20
> Error!
> INSERT INTO gifi (accno,description) VALUES ('0000100', 'Aufwand
> Gesch=EF=BF=BDftsbetrieb')
> ERROR: invalid byte sequence for encoding "UTF8": 0xe46674
> HINT: This error can also happen if the byte sequence does not match th=
e
> encoding expected by the server, which is controlled by
> "client_encoding".
>=20
> --------
>=20
> Next step...
>=20
> I went back to the datasete creation screen and selected Unicode UTF-8
> from the drop down menu.
>=20
> Clicking continue, I get:
>=20
> Error!
> CREATE SEQUENCE id start 10000
> ERROR: relation "id" already exists
>=20
>=20
> ---------
>=20
> Going back to the beginning (my usual mode of operation), with:
>=20
> template1=3D# DROP DATABASE "sql-ledger";
> DROP DATABASE
> template1=3D#=20
>=20
> I then have to go back two steps to the create database screen.
>=20
> But, alas, I get:
>=20
> Error!
>=20
> FATAL: database "sql-ledger" does not exist
>=20
>=20
> Of course it does not exist. I am trying to create it. Why the error..
>=20
>=20

Continuing on from where I left off:

Clicking the 'Delete Dataset' button on the admin.pl page gives:
Error!
Nothing to delete!

At least now sql-ledger knows there is no database.

Now, click on the 'Create Dataset' button:

I get the expected page - so far so good.

Filling in the blanks - sql-ledger, Unicode (UTF-8), and select
'Germany-DATEV-SKR03'; click 'Continue'

The disk buzzes, and.. I get:
Error!
INSERT INTO gifi (accno,description) VALUES ('0000100', 'Aufwand
Gesch=EF=BF=BDftsbetrieb')
ERROR: invalid byte sequence for encoding "UTF8": 0xe46674
HINT: This error can also happen if the byte sequence does not match the
encoding expected by the server, which is controlled by
"client_encoding".

I think I have been here before..