| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Reshat Sabiq" <sabiq(at)purdue(dot)edu> |
| Cc: | <pgadmin-support(at)postgresql(dot)org>, <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: ENCODING (Unicode) |
| Date: | 2003-05-21 07:18:45 |
| Message-ID: | 03AF4E498C591348A42FC93DEA9661B825A1B5@mail.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-novice |
-----Original Message-----
From: Reshat Sabiq [mailto:sabiq(at)purdue(dot)edu]
Sent: 21 May 2003 08:11
To: Dave Page
Cc: pgadmin-support(at)postgresql(dot)org; pgsql-novice(at)postgresql(dot)org
Subject: Re: [pgadmin-support] ENCODING (Unicode)
Thanks. Glad to hear about pgAdminIII...
To follow up on this topic:
Given that i can insert and retrieve Unicode values into either
ASCII-based
or Unicode-based DB, is Unicode-based DB less efficient? I
remember reading
something about it a while ago. I don't see immediately why that
would be the
case though, because special characters are 2 bytes either way,
assuming we
are not simplifying Unicode characters into ASCII.
Sorry, I can't answer that - perhaps someone on
pgsql-general(at)postgresql(dot)org would know?
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2003-05-21 07:50:52 | Re: ENCODING (Unicode) |
| Previous Message | Reshat Sabiq | 2003-05-21 07:10:58 | Re: ENCODING (Unicode) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Louis Foucart | 2003-05-21 07:27:30 | parse error when executing a simple plpgsql function |
| Previous Message | Reshat Sabiq | 2003-05-21 07:10:58 | Re: ENCODING (Unicode) |