SQL_ASCII encoding for PostgreSQL

when creating a PostgreSQL database, different encodings are possible,
SQL_ASCII by default.
Is this important for VisualWorks? Is another encoding better?

On 02/04/07, Rob Vens <[hidden email]> wrote:
> when creating a PostgreSQL database, different encodings are possible,
> SQL_ASCII by default.
> Is this important for VisualWorks? Is another encoding better?

I use SQL_ASCII for my databases but I know that others have gone with
other encodings.  If you want a safe bet, SQL_ASCII is a safe bet.

--
Make the most of your skills - with OpenSkills
http://www.openskills.org/

If you speak anything else then plain english (plat gronings
bijvoorbeeld) then  you better stick with  UTF-8 like VW.

Another way is to request the one your system is using from your Local.

Notice that the Postgres EXDI driver has some nice tests for exotic
languages.

@+Maarten,


Bruce Badger a écrit :
> On 02/04/07, Rob Vens <[hidden email]> wrote:
>> when creating a PostgreSQL database, different encodings are possible,
>> SQL_ASCII by default.
>> Is this important for VisualWorks? Is another encoding better?
>
> I use SQL_ASCII for my databases but I know that others have gone with
> other encodings.  If you want a safe bet, SQL_ASCII is a safe bet.
>

For many purposes, Store will actually deal with encoding even in an ascii database. However, I'd still say utf-8 was a better choice. So, normally you should be able to store non-ascii characters within source code, but if you want to use them in e.g. class and method names, I think you'd need the database to be in an encoding that can handle them. But I wouldn't swear to it either way.

At 09:13 AM 4/5/2007, Maarten Mostert wrote:

If you speak anything else then plain english (plat gronings bijvoorbeeld) then  you better stick with  UTF-8 like VW.

Another way is to request the one your system is using from your Local.

Notice that the Postgres EXDI driver has some nice tests for exotic languages.

@+Maarten,


Bruce Badger a écrit :

On 02/04/07, Rob Vens <[hidden email]> wrote:

when creating a PostgreSQL database, different encodings are possible,
SQL_ASCII by default.
Is this important for VisualWorks? Is another encoding better?

I use SQL_ASCII for my databases but I know that others have gone with
other encodings.  If you want a safe bet, SQL_ASCII is a safe bet.